Time Estimation
- 1 installs
- 1 repo stars
- Updated January 12, 2026
- aviz85/claude-tasks
time-estimation is a Claude skill that estimates task duration from complexity and task type using fixed categories and estimation rules for planning and scheduling.
About
This skill estimates how long a task will take based on its type and complexity, using fixed duration categories from 15 minutes to 4 hours. A developer uses it when planning, scheduling, or running a standup to get consistent estimates. It also adds rules such as doubling uncertain guesses and breaking any task over four hours into subtasks.
- Estimates task duration across five categories from ~15m Quick to ~4h Deep Work
- Provides typical estimates per task type: code, review, communication, research
- Applies rules like the 2x uncertainty rule, context-switching tax, and a 20% coordination buffer
Time Estimation by the numbers
- 1 all-time installs (skills.sh)
- Ranked #2,473 of 3,280 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
time-estimation capabilities & compatibility
- Use cases
- planning · project management
What time-estimation says it does
Estimates time required for tasks based on complexity, type, and patterns. Use when planning, scheduling, or during standup.
If uncertain, estimate 2x your initial guess:
npx skills add https://github.com/aviz85/claude-tasks --skill time-estimationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 1 |
| Last updated | January 12, 2026 |
| Repository | aviz85/claude-tasks ↗ |
What it does
Estimate the duration of a task from its type and complexity to plan and schedule work.
Who is it for?
Producing consistent duration estimates when planning or scheduling tasks
When should I use this skill?
Planning, scheduling, or during a standup
What you get
A duration estimate with a confidence level, adjusted for context switching and uncertainty.
- Duration estimate with confidence level
- Subtask breakdown for tasks over 4 hours
By the numbers
- 5 duration categories from ~15m to ~4h
- Realistic productive hours stated as 4-6 hours/day
- 20% coordination buffer for broken-down tasks
Files
Time Estimation
Estimate task duration for better planning.
Estimation Categories
| Category | Duration | Symbol | Use For |
|---|---|---|---|
| Quick | < 15 min | ~15m | Simple replies, quick fixes, small updates |
| Short | 15-30 min | ~30m | Code reviews, short meetings, simple features |
| Medium | 30-60 min | ~1h | Regular features, documentation, debugging |
| Long | 1-2 hours | ~2h | Complex features, research, planning |
| Deep Work | 2-4 hours | ~4h | Architecture, major features, learning |
Estimation by Task Type
Code Tasks
| Type | Typical Estimate |
|---|---|
| Typo/small fix | ~15m |
| Bug fix (known cause) | ~30m |
| Bug fix (unknown cause) | ~1h to ~2h |
| Small feature | ~1h |
| Medium feature | ~2h |
| Large feature | ~4h or break down |
| Refactoring | ~2h to ~4h |
Review Tasks
| Type | Typical Estimate |
|---|---|
| Small PR (< 100 lines) | ~15m |
| Medium PR (100-500 lines) | ~30m |
| Large PR (500+ lines) | ~1h |
| Document review | ~30m |
| Architecture review | ~1h |
Communication Tasks
| Type | Typical Estimate |
|---|---|
| Quick message | ~15m |
| Email response | ~15m |
| Meeting prep | ~30m |
| Meeting (scheduled) | actual duration |
| Presentation prep | ~2h |
Research Tasks
| Type | Typical Estimate |
|---|---|
| Quick lookup | ~15m |
| Tool evaluation | ~1h |
| Technology research | ~2h |
| Deep learning session | ~4h |
Estimation Rules
The 2x Rule
If uncertain, estimate 2x your initial guess:
- "This seems like 30 min" → Estimate
~1h - "Maybe an hour" → Estimate
~2h
Break Down Large Tasks
If estimate > 4 hours: 1. Break into subtasks 2. Estimate each subtask 3. Add 20% buffer for coordination
Context Switching Tax
Add time for:
- Unfamiliar codebase: +50%
- Interruption-heavy environment: +30%
- Learning new tool: +100%
Daily Capacity
Realistic productive hours: 4-6 hours/day
| Day Type | Available |
|---|---|
| Meeting-heavy day | 2-3 hours |
| Normal day | 4-5 hours |
| Focus day | 6-7 hours |
Planning Rule
- Morning focus: Schedule
~2hdeep work - Afternoon: Schedule
~1htasks - Buffer: Keep 1 hour unscheduled
Estimation Confidence
When presenting estimates:
- High confidence: "~1h" (done similar tasks)
- Medium confidence: "~1h-2h" (some unknowns)
- Low confidence: "needs spike" (too many unknowns)
For low confidence, create a timeboxed research task first: - [ ] Spike: Investigate X ~1h → Then estimate the real task
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
What are the estimation categories?
Quick (~15m), Short (~30m), Medium (~1h), Long (~2h), and Deep Work (~4h).
What is the 2x rule?
If uncertain, estimate twice your initial guess - a 30-minute hunch becomes ~1h and an hour becomes ~2h.