time-estimation

Estimate task durations using category mapping and planning heuristics.

1|1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/aviz85/claude-tasks --skill time-estimation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: time-estimation
Source: https://github.com/aviz85/claude-tasks/tree/main/.claude/skills/time-estimation
Command: npx skills add https://github.com/aviz85/claude-tasks --skill time-estimation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Time estimation for tasks is often manual, inconsistent, and error-prone, leading to overcommitment or underplanning.

Core Features & Use Cases

  • Category-based duration estimates (Quick, Short, Medium, Long, Deep Work) for tasks in any project.
  • Rule-driven planning support for standups, iterations, and backlog grooming (including 2x rule and task breakdown).
  • Real-world example: during standup, assign estimated durations to new tasks to maintain a realistic day plan.

Quick Start

To start using time-estimation, tag tasks with an estimated duration (e.g., - [ ] Implement login page ~1h) and reference the rule set to refine estimates. You can apply estimates when creating items, during reviews, or while planning your day.

Frequently Asked Questions about time-estimation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I estimate task duration for agile sprint planning?

Task duration estimation maps backlog items to structured categories like Quick, Short, Medium, Long, and Deep Work. It applies planning heuristics such as the 2x rule and task breakdowns to produce realistic sprint schedules.

What is the 2x rule for time estimation?

The 2x rule is a planning heuristic that suggests doubling your initial time estimate to account for unforeseen complexities. It helps prevent overcommitment and underplanning during backlog grooming and standups.

How do I tag tasks with estimated durations for daily standups?

You tag tasks by appending an estimated duration directly to the task item, such as writing - [ ] Implement login page ~1h. This enforces structured category mapping for a realistic day plan during reviews.

Can I use time estimation for backlog grooming across different projects?

Yes, time estimation applies to backlog work across projects by mapping tasks to duration categories. It provides rule-driven guidance for standups, iterations, and backlog grooming regardless of the project scope.

What are the task duration categories used for scheduling?

The scheduling categories are Quick, Short, Medium, Long, and Deep Work. This structured mapping ensures consistent duration estimates and prevents error-prone manual guessing during project planning.

Why does time estimation prevent overcommitment in agile planning?

Time estimation prevents overcommitment by replacing manual guessing with structured rules like category mapping and the 2x rule. It enforces task breakdowns to keep iteration schedules realistic and manageable.