story-point-estimator
A methodology for systematically estimating user story points. Used during sprint planning for tasks such as 'story point estimation,' 'SP calculation,' 'effort estimation,' 'velocity calculation,' and 'planning poker.' Note: Updating actual Jira tickets or facilitating team meetings is outside the scope of this skill.
Best use case
story-point-estimator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
A methodology for systematically estimating user story points. Used during sprint planning for tasks such as 'story point estimation,' 'SP calculation,' 'effort estimation,' 'velocity calculation,' and 'planning poker.' Note: Updating actual Jira tickets or facilitating team meetings is outside the scope of this skill.
Teams using story-point-estimator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/story-point-estimator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How story-point-estimator Compares
| Feature / Agent | story-point-estimator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
A methodology for systematically estimating user story points. Used during sprint planning for tasks such as 'story point estimation,' 'SP calculation,' 'effort estimation,' 'velocity calculation,' and 'planning poker.' Note: Updating actual Jira tickets or facilitating team meetings is outside the scope of this skill.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Story Point Estimator A skill that enhances the effort estimation capabilities of sprint-planner and story-writer. ## Target Agents - **sprint-planner** — Plans sprint capacity and story allocation - **story-writer** — Evaluates complexity when writing user stories ## Fibonacci Scale Reference | SP | Complexity | Uncertainty | Effort | Example | |----|-----------|-------------|--------|---------| | 1 | Very Low | None | A few hours | Text change, config value update | | 2 | Low | Very Low | Half a day | Simple UI component addition | | 3 | Moderate | Low | 1 day | Single CRUD API, simple screen | | 5 | Medium | Moderate | 2-3 days | Complex business logic, external API integration | | 8 | High | High | 1 week | New feature module, authentication system | | 13 | Very High | Very High | 1-2 weeks | Architecture change, large-scale refactoring | | 21+ | Needs Decomposition | - | - | Story is too large — decomposition required | ## Complexity Assessment Dimensions ### Three-Dimensional Assessment Model ``` Final SP = max(Technical Complexity, Domain Complexity, Uncertainty) 1. Technical Complexity - Scope of code changes (number of files, number of layers) - Technical difficulty (algorithms, concurrency, security) - Testing difficulty (edge cases, integration tests) 2. Domain Complexity - Number of business rules - Exception handling scenarios - Whether stakeholder approval is required 3. Uncertainty - Whether a technical spike is needed - External dependencies (APIs, libraries, infrastructure) - Clarity of requirements ``` ## Velocity Calculation ``` Velocity = Total SP completed in a sprint Stable velocity calculation: - Average of the last 3-5 sprints - Average after removing outliers (extreme values) - Or use the median Example: Sprint 1: 32 SP Sprint 2: 28 SP Sprint 3: 35 SP Sprint 4: 15 SP (outlier due to vacations, etc.) Sprint 5: 30 SP Average (outliers removed): (32+28+35+30)/4 = 31.25 SP ``` ## Sprint Capacity Calculation ``` Sprint Capacity = Velocity x Availability Rate Availability rate calculation: Total person-days = Team size x Sprint days Unavailable = Vacations + Training + Meetings + On-call Available person-days = Total person-days - Unavailable Availability rate = Available person-days / Total person-days Example: 5 team members x 10 days = 50 person-days 3 vacation days + 5 meeting days = 8 days Available: 42 days → Availability rate 84% Capacity = 31 SP x 0.84 ≈ 26 SP Buffer: Stable team: Plan 80% of capacity (20% buffer) New team/uncertain: Plan 70% of capacity (30% buffer) ``` ## User Story Decomposition Criteria ``` Decomposition is mandatory for stories of 13 SP or more: Decomposition strategies: 1. By workflow stage "User makes a payment" → - Select payment method - Enter payment information - Process payment - Confirm payment 2. By data variation "Support multiple formats" → - JSON support - CSV support - XML support 3. By user type "User logs in" → - Email login - Social login - SSO login 4. By CRUD operation "Product management" → - List products - Create product - Update product - Delete product 5. By Happy/Sad path - Normal flow - Error handling - Edge cases ``` ## Estimation Bias Prevention ``` 1. Anchoring effect prevention → Simultaneous reveal (planning poker style) → Highest/lowest estimators explain their rationale 2. Optimism bias prevention → Consider "worst case" scenarios → Include time for testing/review/deployment 3. Parkinson's Law prevention → SP measures complexity, not time → "3 SP" not "2 days" 4. Reference point alignment → Maintain team-wide reference stories → Anchors like "Login API = 3 SP" ``` ## Deliverable Template ```markdown ## Story Point Estimation Results ### Velocity: [N] SP/sprint ### Available Capacity: [N] SP (including [M]% buffer) ### Estimation Results | Story | Technical | Domain | Uncertainty | SP | Notes | |-------|-----------|--------|-------------|-----|-------| ### Sprint Allocation | Sprint | Total SP | Story List | |--------|----------|------------| | Sprint 1 | 26/31 | [list] | | Sprint 2 | 28/31 | [list] | ```
Related Skills
visual-storytelling
Visual Storytellingof Story Design, Text writing, AI Image (Gemini), HTML Layout, Integration Editing an agent team collaborates to production to line. 'Visual Story ', 'in Planning', 'Image+ combination', 'Visual in', 'Story page production', ' Story', 'Visual Planning', 'Image in', ' Story', 'Visual Narrative' etc. Imageand Text Storytelling productionin . Text Image casein Layout Integration . , video Editing, DTP, (JS ) of .
audio-storytelling
Audio storytelling skill used by the podcast scriptwriter and show note editor. Provides narrative structure, pacing, and sound design methodologies that maximize listener immersion in an audio-only medium. Use this skill's knowledge for 'audio narrative,' 'listener retention,' 'story arc,' 'sound design,' and similar requests.
sustainability-audit
Full audit pipeline for ESG/sustainability where an agent team collaborates to generate environmental, social, and governance assessments along with an integrated report and improvement plan. Use this skill for requests such as 'run an ESG audit', 'write a sustainability report', 'ESG assessment', 'carbon emissions calculation', 'ESG rating diagnosis', 'governance review', 'social responsibility assessment', 'GRI report', 'TCFD disclosure', 'ESG improvement plan', and other ESG/sustainability tasks. Also supports assessment of specific pillars (E/S/G) only or improving existing reports. However, actual on-site audit execution, third-party verification certificate issuance, ESG rating agency score changes, and carbon credit trading are outside the scope of this skill.
materiality-assessment
ESG materiality assessment matrix. Referenced by the esg-reporter and improvement-planner agents when evaluating ESG issue materiality and setting priorities. Use for 'materiality assessment', 'importance analysis', or 'Materiality Matrix' requests. Stakeholder surveys and external certification are out of scope.
ghg-protocol
GHG Protocol detailed guide. Referenced by the environmental-analyst agent when calculating and reporting greenhouse gas emissions. Use for 'GHG Protocol', 'carbon emissions', 'Scope 1/2/3', or 'carbon footprint' requests. Carbon credit trading and CDM project execution are out of scope.
citation-standards
Academic citation and reference standards guide. Referenced by the paper-writer and submission-preparer agents when composing citations and references. Use for 'citation format', 'APA', or 'references' requests. Original paper retrieval and professional database access are out of scope.
academic-paper
Full research pipeline for academic paper writing where an agent team collaborates to generate research design, experiment protocols, analysis, manuscript writing, and submission preparation. Use this skill for requests such as 'write an academic paper', 'research paper writing', 'help me write a paper', 'design a study', 'run statistical analysis', 'prepare journal submission', 'manuscript writing', 'research methodology design', 'hypothesis testing', 'academic writing', and other academic research paper tasks. Also supports analysis, rewriting, and submission preparation when existing data or drafts are available. However, actual data collection execution, official IRB submission, journal system login and upload, and running actual statistical software are outside the scope of this skill.
product-copy-formulas
Product copy formula library. Referenced by the detail-page-writer and marketing-manager agents when writing purchase-driving copy. Use for 'product copy', 'marketing copy', or 'ad copy' requests. Ad placement and design mockup creation are out of scope.
ecommerce-launcher
Full launch pipeline for e-commerce products where an agent team collaborates to generate product planning, detail pages, pricing strategy, marketing, and CS setup all at once. Use this skill for requests such as 'launch an e-commerce product', 'prepare a product launch', 'register a product on Naver Smart Store', 'launch on Coupang', 'create a detail page', 'develop a pricing strategy', 'create a marketing plan', 'launch prep', 'product planning brief', 'e-commerce CS manual', and other e-commerce product launch tasks. Also supports supplementing pricing/marketing/CS even when existing briefs or detail pages are provided. However, actual platform API integration (automated product registration), payment system development, logistics system integration, and real-time order management are outside the scope of this skill.
conversion-optimization
Purchase conversion optimization framework. Referenced by the detail-page-writer and pricing-strategist agents when designing detail pages and pricing with a conversion focus. Use for 'conversion rate optimization', 'CRO', or 'purchase psychology' requests. A/B testing tool setup and funnel automation are out of scope.
real-estate-analyst
Real estate investment analysis pipeline. An agent team collaborates to produce market research, location analysis, profitability analysis, risk assessment, and investment reports. Use this skill for requests such as 'analyze this real estate', 'apartment investment analysis', 'studio apartment yield', 'real estate market research', 'location analysis', 'real estate investment report', 'buy vs lease', 'reconstruction investment analysis', 'commercial property yield analysis', and other general real estate investment analysis tasks. Actual purchase contracts, brokerage services, interior design, and property management are outside the scope of this skill.
location-scoring
Location scoring scorecard. Referenced by the location-analyst agent for systematic real estate location evaluation. Use for requests involving 'location analysis', 'location assessment', or 'commercial area analysis'. On-site inspections and surveying are out of scope.