capability-estimate

Estimates refined user stories using the team's adopted estimation methodology.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/learnn-com/engineering-kb --skill capability-estimate-learnn-com
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capability-estimate
Source: https://github.com/learnn-com/engineering-kb/tree/main/.skills/capability-estimate
Command: npx skills add https://github.com/learnn-com/engineering-kb --skill capability-estimate-learnn-com

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often estimate user stories inconsistently or skip estimation entirely, leading to unreliable sprint planning. This Skill applies the team's adopted estimation methodology to refined stories in a consistent, idempotent way, recording the result directly in the PM tool. ## Core Features & Use Cases - Methodology-driven estimation: Supports complexity, time-based, AI-assisted, forecast, and hybrid methods, reading the adopted approach from the team's way-of-working document. - Idempotent execution: Detects an existing estimate and confirms it instead of re-estimating, unless the developer explicitly requests re-estimation. - PM tool integration: Writes the approved estimate back to the story issue and supports composition by /process-refine-story. - Use Case: A developer finishes refining story #142 with acceptance criteria and runs the estimation flow; the Skill loads the story, applies the team's complexity-based method, proposes 5 story points with a confidence level, and records it after approval. ## Quick Start Estimate story #142 using the team's adopted estimation methodology and record the approved estimate in the PM tool.

Frequently Asked Questions about capability-estimate

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

FAQPage Schema
How do I estimate a user story with story points?▼

Provide the story ID and the Skill loads the story from the PM tool, verifies it has acceptance criteria, then applies the adopted methodology such as complexity-based estimation with a Fibonacci scale. You review and approve the proposed estimate before it is recorded.

What estimation methods does this Skill support?▼

It supports five methods: complexity-based, time-based, AI-assisted, forecast-based, and hybrid. You can override the method with the $method argument, or it defaults to the methodology adopted in the team's way-of-working document.

What happens if a story already has an estimate?▼

The Skill is idempotent: it detects the existing estimate and presents it for confirmation instead of re-estimating. Re-estimation only occurs when the developer explicitly requests it.

Can I estimate a story that has no acceptance criteria?▼

The Skill halts if the story is not in a refined state, since estimation requires acceptance criteria. If criteria are missing it warns that estimation may be inaccurate and suggests refining the story first.

What happens if the PM tool is not accessible?▼

The Skill degrades gracefully by presenting the estimate and asking the developer to record it manually. It also falls back to developer judgment if estimation guidelines are unavailable.