skills.rest
AcidicSoil
AcidicSoilCOMMUNITY
Explore all skills by this author →
𝕏@d1rt7d4t4GitHub

estimate-stories

Calculate story points from Complexity, Effort, and Risk inputs.

1|Updated Oct 19, 2025
Search Tags:#planning#agile#estimation#complexity#risk#story-points#effort
One-click install
npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill estimate-stories-acidicsoil
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: estimate-stories
Source: https://github.com/AcidicSoil/lms-llmsTxt/tree/main/.claude/skills/estimate-stories
Command: npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill estimate-stories-acidicsoil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Story point estimation is often subjective and inconsistent; this skill provides a structured method to convert backlog item details into a reproducible numeric score, improving planning accuracy.

Core Features & Use Cases

  • Structured formula: Story Points = (Complexity × Effort) + Risk
  • Explicit inputs: Complexity (1-5), Effort (1-5), and Risk (0-3) per story
  • Rationale documentation: Automatically records estimation reasoning for calibration and audit trails
  • Primary use cases: backlog grooming, sprint planning, velocity forecasting, and cross-team estimation comparisons

Quick Start

Provide a story context file or summary and set the initial Complexity, Effort, and Risk values to compute points.

Frequently Asked Questions about estimate-stories

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

FAQPage Schema
How do I calculate story points for agile backlog grooming?▼

Calculate story points for backlog grooming using a fixed formula: (Complexity × Effort) + Risk. Input Complexity (1-5), Effort (1-5), and Risk (0-3) to produce a reproducible numeric score for sprint planning.

What is the best way to make agile estimation consistent across a team?▼

Structured story point estimation ensures consistency by applying a fixed formula. Using explicit Complexity, Effort, and Risk inputs removes subjectivity, yielding reproducible scores for cross-team velocity comparisons.

How does story point estimation handle project risk and complexity?▼

Story point estimation handles risk and complexity by factoring them into a fixed formula. Complexity (1-5) is multiplied by Effort (1-5), and Risk (0-3) is added to compute the final story points.

Can I document estimation rationale for sprint planning audits?▼

Yes, you can document estimation rationale for sprint planning audits. The process automatically records the reasoning behind each story point calculation, providing a clear audit trail for future calibration.

Does velocity forecasting require structured story point inputs?▼

Velocity forecasting requires structured story point inputs to predict future sprint capacity accurately. Converting backlog details into reproducible numeric scores ensures velocity calculations remain reliable across planning cycles.

Related Skills

Explore More Product & Management Skills→
wtthorntonwtthornton
4

planner

Creates user stories, epics, and tasks with Fibonacci point estimates.

Community
Advanced
ConnectiveTCSConnectiveTCS

sprint-planner

Plan sprints with story estimation, capacity planning, and goal definition.

Community
Intermediate
markus41markus41
1

scrum

Facilitate Scrum ceremonies and manage sprint backlog with agile estimation.

Community
Basic
dipandhali2021dipandhali2021

task-estimation

Estimate software tasks with story points, t-shirt sizing, and planning poker.

Community
Advanced