task-estimator

Decompose project epics into tasks with three-point estimates and dependency planning.

8|1|Updated Feb 27, 2026

Search Tags:#risk-management #velocity #sprint-planning #story-points #task-breakdown #planning-poker #estimate

Ready to run

npx skills add https://github.com/thesaifalitai/claude-setup --skill task-estimator-thesaifalitai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-estimator
Source: https://github.com/thesaifalitai/claude-setup/tree/main/skills/task-estimator
Command: npx skills add https://github.com/thesaifalitai/claude-setup --skill task-estimator-thesaifalitai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Task Estimator helps product and engineering teams break ambiguous initiatives into concrete tasks, assign estimates, and plan sprint work with realistic timelines.

Core Features & Use Cases

Decompose epics into user stories and subtasks with clear acceptance criteria.
Apply Fibonacci-based story-point estimation, planning poker, and T-shirt sizing to gauge effort.
Plan capacity, compute velocity, and forecast release timelines for reliable delivery.
Identify hidden complexity, estimation bias, and dependencies to surface risks early.
Create a structured backlog with dependencies and sequencing for vertical slices.

Quick Start

Provide your project epic and constraints to generate a step-by-step task breakdown, estimates, and an initial sprint plan.

Frequently Asked Questions about task-estimator

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

FAQPage Schema

How do I break down project epics into actionable tasks for sprint planning?▼

To break down project epics for sprint planning, decompose the initiative into user stories and subtasks with clear acceptance criteria. This task breakdown process enables reliable sprint planning by transforming ambiguous epics into structured, actionable deliverables.

What is the best way to estimate story points for backlog items?▼

The best way to estimate story points is by applying Fibonacci-based sizing, planning poker, and T-shirt sizing. These estimation techniques gauge development effort while helping teams identify hidden complexity and estimation bias early in the sprint planning process.

How do I forecast release timelines using team velocity and capacity?▼

You forecast release timelines by computing team velocity and planning capacity against your estimated backlog. This velocity planning approach maps story points to available sprint capacity, generating realistic delivery timelines for multiple engineering teams.

Can I map dependencies and hidden complexity when doing task breakdown?▼

Yes, task breakdown includes mapping dependencies and hidden complexity to surface risks early. By identifying hidden work and sequencing vertical slices, you can create a structured backlog that accounts for cross-team dependencies and minimizes delivery risks.

Does three-point estimation work for agile sprint planning and task sizing?▼

Three-point estimation works for agile sprint planning by providing optimistic, pessimistic, and most likely effort scenarios. When combined with vertical slicing and dependency planning, it ensures deliverable increments are realistically sized for reliable sprint execution.