estimating-work

Estimate development effort using story points and T-shirt sizing.

111|18|Updated Dec 17, 2025

Search Tags:#planning #estimation #story-points #planning-poker

Ready to run

npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill estimating-work

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: estimating-work
Source: https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/product/estimating-work
Command: npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill estimating-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides relative estimation techniques and planning guidance for sprints and roadmaps.

Core Features & Use Cases

Estimation Scales: Story points and T-shirt sizing.
Uncertainty & Risk: Factors to consider and buffer guidance.
Use Case: Estimate a feature backlog with planning poker.

Quick Start

Prepare a 3-point story with a risk buffer for a new signup flow.

Frequently Asked Questions about estimating-work

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

FAQPage Schema

How do I estimate development effort using story points?▼

Story points represent relative effort and complexity, not hours. Compare tasks to reference stories of known size, then assign points through Planning Poker or consensus. This approach accounts for uncertainty and risk better than time-based estimates.

What's the best way to handle uncertainty in task estimation?▼

Use Three-Point Estimation to capture optimistic, realistic, and pessimistic scenarios, then apply buffers for risk and scope changes. Build uncertainty into your relative sizing scheme rather than padding hours.

Can I use T-shirt sizing instead of story points for estimation?▼

Yes. T-shirt sizing (XS, S, M, L, XL) works as an alternative relative scale when story points feel too granular. Both techniques support the same Planning Poker and reference-story workflows for sprint planning and roadmapping.

How do I run Planning Poker to estimate a feature backlog?▼

Gather the team, present a backlog item, have each member independently assign story points or sizing, reveal simultaneously, discuss outliers, and reach consensus. This collaborative method surfaces hidden complexity and reduces estimation bias.

Why should I estimate relative size instead of hours?▼

Relative estimation sidesteps false precision and individual velocity variation. Story points and T-shirt sizes scale with team context and capture complexity-driven effort, making forecasts more reliable across sprints than hour-based guesses.

How do I account for scope changes and overhead in estimation?▼

Track scope drift separately from effort sizing, and factor overhead (meetings, interrupts, infrastructure work) into team capacity rather than individual task estimates. Adjust reference stories and buffers as scope and overhead patterns emerge.