estimation-and-sizing

Apply standardized sizing methods to estimate development effort across planning horizons.

2|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/dreamingechoes/dx-toolkit --skill estimation-and-sizing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimation-and-sizing
Source: https://github.com/dreamingechoes/dx-toolkit/tree/main/templates/skills/estimation-and-sizing
Command: npx skills add https://github.com/dreamingechoes/dx-toolkit --skill estimation-and-sizing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and forecasting development work across teams is hard without consistent sizing. This skill provides structured methods (T-shirt sizing, story points, reference stories, and velocity tracking) to align estimates and improve predictability.

Core Features & Use Cases

  • T-shirt sizing for high-level planning (epics and roadmaps)
  • Story points for sprint-level estimation and planning
  • Reference stories to calibrate sizing across the team
  • Velocity tracking to forecast delivery and rebalance scope
  • Calibration cycles to improve estimate accuracy over time

Quick Start

Choose a sizing method for each planning horizon and document reference stories to calibrate estimates.

Frequently Asked Questions about estimation-and-sizing

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

FAQPage Schema
What is the best way to standardize story points and effort estimates across an agile team?

To standardize effort estimates, apply consistent sizing methods like story points and T-shirt sizes across planning horizons, using reference stories to calibrate sizing and align team forecasts.

How do I calibrate story points using reference stories for sprint planning?

Calibrate story points by documenting reference stories as baselines, comparing new backlog items against them, and tracking actuals versus estimates to maintain a rolling velocity baseline.

When should I use T-shirt sizing versus story points for agile estimation?

Use T-shirt sizing for high-level epic and roadmap planning, and apply story points for sprint-level estimation, ensuring consistent effort sizing methods across different planning horizons.

How do you track velocity to forecast delivery and rebalance scope?

Track velocity by maintaining a rolling baseline from completed sprints, comparing actuals against initial estimates, and running regular calibration cycles to improve forecast accuracy and rebalance scope.

Why are my agile estimates inconsistent and how can I improve predictability?

Agile estimates become inconsistent without standardized sizing. Improve predictability by documenting reference stories, applying uniform estimation methods, and tracking actuals versus estimates for calibration.