Story Point Estimator

Estimates story points for tasks using Fibonacci and fine-grained scales with complexity adjustments.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/sparkst/sparkry-claude-skills --skill story-point-estimator-sparkst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Story Point Estimator
Source: https://github.com/sparkst/sparkry-claude-skills/tree/main/plugins/dev-workflow/skills/story-point-estimator
Command: npx skills add https://github.com/sparkst/sparkry-claude-skills --skill story-point-estimator-sparkst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle to produce consistent, defensible effort estimates during sprint planning and task breakdown, often falling back on vague time guesses or padded numbers. This Skill provides a calibrated, repeatable estimation process anchored to a fixed baseline so every estimate is comparable and justified. ## Core Features & Use Cases - Dual Estimation Scales: Fibonacci scale (1-21) for planning and roadmap sizing, plus a fine-grained scale (0.05-5) for implementation-level coding tasks. - Complexity Adjustment Factors: Structured modifiers for multi-system coordination, compliance requirements, integrations, data migrations, and unfamiliar domains. - Structured Output Template: Produces a breakdown table, adjustment rationale, confidence level, and risk assessment for every estimate. - Use Case: During sprint planning, a team needs to size a feature touching multiple services with a database migration. The Skill decomposes it into components, applies the migration and multi-system adjustments, and flags anything over 13 SP for further breakdown. ## Quick Start Estimate the story points for adding a payment integration with webhook handling and a database schema migration.

Frequently Asked Questions about Story Point Estimator

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

FAQPage Schema
How do I estimate story points for a software task?▼

Decompose the task into components, estimate each relative to the 1 SP baseline (a simple authenticated API), then apply complexity adjustments for factors like integrations or migrations. Sum the results and round to valid scale values.

What is the difference between Fibonacci and fine-grained story point scales?▼

The Fibonacci scale (1, 2, 3, 5, 8, 13, 21) is used for feature planning and sprint sizing, while the fine-grained scale (0.05 to 5) is used for implementation-level coding tasks within a sprint. Each has its own breakdown threshold.

When should a story point estimate be broken down further?▼

Break down any item exceeding 13 SP on the planning scale or 5 SP on the coding scale. Large estimates hide uncertainty and make tracking unreliable, so decomposition into smaller components is mandatory at those thresholds.

Why should teams avoid time-based estimates instead of story points?▼

Time estimates anchor to individual speed and create false precision, while story points measure relative complexity against a fixed baseline. This keeps estimates comparable across team members and over time.

What complexity factors increase a story point estimate?▼

Adjustments include multi-system coordination (+1-2 SP), compliance requirements like HIPAA or GDPR (+1 SP), third-party integrations (+1-3 SP), data migrations (+1-2 SP), performance constraints (+1 SP), and unfamiliar domains (+1 SP).