Story Point Estimator

Guide agile teams in estimating story points using Planning Poker and Fibonacci sequencing.

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Razmik-Kutinava/test.admin_logistic_v8 --skill story-point-estimator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Story Point Estimator
Source: https://github.com/Razmik-Kutinava/test.admin_logistic_v8/tree/main/.claude/skills/story-point-estimator
Command: npx skills add https://github.com/Razmik-Kutinava/test.admin_logistic_v8 --skill story-point-estimator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps agile teams accurately and consistently estimate the complexity, effort, and uncertainty of user stories, leading to better sprint planning and predictable delivery.

Core Features & Use Cases

  • Relative Sizing: Utilizes established principles like the Fibonacci sequence for consistent estimation.
  • Estimation Techniques: Supports Planning Poker, T-Shirt Sizing, and Three-Point Estimation.
  • Use Case: A development team can use this Skill during backlog refinement to collaboratively estimate a new feature, ensuring everyone understands the scope and effort involved before committing to a sprint.

Quick Start

Use the Story Point Estimator skill to help estimate the complexity of a new user story.

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 agile story points for backlog refinement?

Estimating agile story points during backlog refinement involves using relative sizing techniques like Fibonacci sequencing and Planning Poker to collaboratively assess complexity, effort, and uncertainty. This approach ensures accurate sprint planning and predictable delivery.

What is the best way to run Planning Poker for scrum estimation?

The best way to run Planning Poker for scrum estimation is to apply Fibonacci sequencing and relative sizing principles. This helps teams collaboratively evaluate story complexity, effort, and uncertainty, ultimately improving sprint predictability and team calibration.

How does relative sizing improve sprint planning predictability?

Relative sizing improves sprint planning predictability by using techniques like the Fibonacci sequence to evaluate story complexity and effort. This methodology reduces uncertainty and ensures consistent team calibration for accurate sprint delivery.

Can I use T-Shirt sizing alongside Fibonacci sequencing for agile estimation?

Yes, you can use T-Shirt sizing alongside Fibonacci sequencing for agile estimation. Both are supported relative sizing techniques that help teams evaluate story complexity and effort during backlog refinement and sprint planning.

When should my development team use Three-Point Estimation for user stories?

Your development team should use Three-Point Estimation for user stories when assessing high uncertainty or complex effort requirements. This technique complements Planning Poker by providing risk analysis to improve overall sprint predictability.