story-point-estimation

Estimate work using calibrated story points and velocity-based forecasting.

1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/SSiertsema/claude-code-plugins --skill story-point-estimation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-point-estimation
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/story-point-estimation/skills/story-point-estimation
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill story-point-estimation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Estimating work becomes subjective and inconsistent without a shared size language. This skill defines what story points mean, establishes calibration through reference stories, and provides velocity-based forecasting to improve planning reliability.

Core Features & Use Cases

  • Defines what a point represents across complexity, uncertainty, and effort.
  • Calibrates estimates with 3–5 reference stories covering small to large sizes.
  • Forecasts delivery using velocity while surfacing anti-patterns to help teams improve.

Quick Start

Provide your team context and the stories to estimate, then initiate calibration to establish reference points.

Frequently Asked Questions about story-point-estimation

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

FAQPage Schema
How do I calibrate agile story points for consistent team estimation?

Calibrate agile story points by defining what a point represents across complexity, uncertainty, and effort, then anchor your scale using 3–5 reference stories covering small to large sizes.

What is the best way to forecast delivery using velocity?

Forecast delivery using velocity by tracking completed story points per iteration and projecting that throughput against your calibrated backlog to estimate future completion timelines.

How do I define story points across complexity, uncertainty, and effort?

Define story points using a three-point dimension framework that evaluates task complexity, uncertainty, and effort, establishing a shared sizing language to reduce subjective inconsistencies during planning.

Why does our agile estimation become subjective and inconsistent across the team?

Agile estimation becomes subjective and inconsistent without a shared size language, which is why defining point meanings and calibrating against reference stories is critical for reliable planning.

What anti-patterns should I detect during story point estimation?

Detect anti-patterns during story point estimation by monitoring velocity-based forecasting for inconsistencies, ensuring your calibrated reference stories and Fibonacci sizing remain aligned over time.

Can I apply story point estimation to design and engineering tasks?

Yes, you can apply story point estimation to planning, calibration, and forecasting across product, design, and engineering tasks within teams using the calibrated reference framework.