task-estimation_skill

Overview

This skill estimates software development tasks using proven agile techniques like story points, planning poker, and T-shirt sizing. It helps teams produce relative, consensus-driven estimates for sprints, roadmaps, and resource planning. The skill includes risk and uncertainty adjustments and a template for clear estimation documentation.

How this skill works

It guides teams through relative estimation using a Fibonacci-based story points scale (1,2,3,5,8,13,21+) and quick T-shirt sizing for early backlog triage. Use planning poker to surface assumptions and reach team consensus through rounds of discussion and re-voting. The skill also applies simple buffers for risk and uncertainty to convert base estimates into adjusted final estimates and provides a markdown template for recording outcomes.

When to use it

• Sprint planning to pick work for the next iteration
• Roadmap refinement and long‑term planning
• Initial backlog triage when fast, directional estimates are needed
• Resource and capacity planning based on team velocity
• When a story feels large (13+ points) and should be split

Best practices

• Estimate relatively, not in absolute hours — use story points or sizes
• Always aim for team consensus via planning poker or group discussion
• Break down anything 13 points or larger into smaller stories
• Reference past similar stories and team velocity when planning
• Apply a risk and uncertainty buffer rather than strict add‑ons

Example use cases

• Estimate a new feature composed of frontend UI, API, and tests with a 5-point breakdown
• Quickly size a backlog during roadmap planning using T-shirt categories (S/M/L)
• Run planning poker for a complex story to reveal differing assumptions and resolve them
• Adjust estimates for a medium-risk task by applying a 1.3x risk buffer and uncertainty factor
• Split an epic (21+ points) into smaller user stories before sprint assignment