Does this skill convert story points directly into hours?

No, it follows agile best practices by focusing on relative complexity, effort, and uncertainty rather than absolute time estimates to maintain planning accuracy.

What happens if a story is estimated above 13 points?

The skill identifies large estimates as red flags and provides strategies for breaking the story down into smaller, more predictable tasks that fit within a single sprint.

Can this skill help with estimating software bugs?

Yes, it includes specific guidelines for bug estimation, ranging from simple 1-point typo corrections to 8+ point architectural issues requiring investigation.

How does the skill handle team disagreements during estimation?

It provides a structured Planning Poker process that encourages discussing high and low estimates to uncover hidden assumptions and reach a team consensus.

Agile Story Point Estimator

Name: Agile Story Point Estimator
Author: Razmik-Kutinava

byRazmik-Kutinava

Collaboration Tools

Facilitates accurate agile estimation and backlog refinement using standardized techniques like Fibonacci sequencing and Planning Poker.

About

This skill transforms Claude into an expert agile consultant, helping development teams navigate the complexities of story point estimation. It provides structured frameworks for relative sizing, technical complexity assessment, and risk analysis, ensuring sprint planning is grounded in data rather than guesswork. Whether you are running a Planning Poker session, breaking down large epics, or calibrating team velocity, this skill offers the templates and best practices needed to improve delivery predictability and foster team consensus.

Key Features

Planning Poker and Three-Point estimation methodologies
0 GitHub stars
Standardized Fibonacci and T-Shirt sizing scales
Detailed user story and bug estimation templates
Multi-dimensional complexity and risk assessment framework
Velocity tracking and team calibration strategies

Use Cases

Standardizing estimation logic across distributed engineering teams
Facilitating backlog refinement and sprint planning sessions
Breaking down high-complexity epics into manageable user stories

About

Key Features

Planning Poker and Three-Point estimation methodologies
0 GitHub stars
Standardized Fibonacci and T-Shirt sizing scales
Detailed user story and bug estimation templates
Multi-dimensional complexity and risk assessment framework
Velocity tracking and team calibration strategies

Use Cases

Standardizing estimation logic across distributed engineering teams
Facilitating backlog refinement and sprint planning sessions
Breaking down high-complexity epics into manageable user stories