skills.rest
hoshiyar-singh8
hoshiyar-singh8COMMUNITY
Explore all skills by this author →
GitHub

story-point-sizing

Estimate and validate software task story points using a 1/2/3 scale with auto-splitting rules.

Updated Mar 16, 2026
Search Tags:#agile#estimation#complexity#guidelines#sprint-planning#story-points#task-splitting
One-click install
npx skills add https://github.com/hoshiyar-singh8/SprintPlanner --skill story-point-sizing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-point-sizing
Source: https://github.com/hoshiyar-singh8/SprintPlanner/tree/main/skills/story-point-sizing
Command: npx skills add https://github.com/hoshiyar-singh8/SprintPlanner --skill story-point-sizing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Story-point-sizing provides a structured approach to estimate and validate the effort of software tasks using a consistent 1/2/3 scale.

Core Features & Use Cases

  • Hard Rules: Maximum 3 SP per task; auto-split triggers for complex tasks; clear acceptance criteria.
  • Estimation Signals: 1 SP signals (e.g., small changes to existing code), 2 SP signals (e.g., API client method with error handling), 3 SP signals (e.g., full module integration).
  • Complexity Signals and Checklist: guidelines to assess task scope, file impact, testability.
  • SP vs Hero Gen Eligibility: guidance on when Hero Gen can handle tasks.

Quick Start

Use these guidelines to estimate tasks and automatically split work when estimates exceed 3 SP.

Frequently Asked Questions about story-point-sizing

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

FAQPage Schema
How do I estimate story points for sprint planning using a 1/2/3 scale?▼

Story point estimation uses a 1/2/3 scale where 1 SP signals small changes to existing code, 2 SP covers API client methods with error handling, and 3 SP indicates full module integration for agile sprint planning.

When should I split tasks during agile task complexity assessment?▼

Task splitting triggers automatically when estimates exceed 3 SP during agile task complexity assessment. The maximum limit is 3 SP per task, and auto-splitting rules enforce breaking down complex work to maintain effort governance.

What story point signals indicate full module integration complexity?▼

Full module integration complexity signals 3 SP in story point estimation. Other complexity signals include file impact scope and testability checklist guidelines to assess task effort accurately during sprint planning.

Does story point sizing enforce a maximum SP limit per task for team workflows?▼

Story point sizing enforces a maximum of 3 SP per task to align with team workflows. It applies hard rules including auto-split triggers for complex tasks and clear acceptance criteria to guide effort assessment.

Can I use story point guidelines to check task eligibility for code generation tools?▼

Story point guidelines include SP vs Hero Gen eligibility guidance to determine when code generation can handle tasks. Estimation signals help assess task scope, file impact, and testability before assigning work.

Related Skills

Explore More Software Engineering Skills→
Phife726Phife726

sprint-planner

Coordinate sprint planning, story point estimation, and capacity calculation for agile teams.

Community
Intermediate
ngochuy13ngochuy13

sprint-planner

Plan Agile sprints by selecting backlog items and calculating team capacity with buffers.

Community
Intermediate
gabergergaberger
4

github-project-management

Automate GitHub project governance with swarm coordination for issues, boards, and sprints.

Community
Advanced
bbolek-apbbolek-ap

create-estimate

Produce structured effort estimates with T-shirt sizing and three-point estimation.

Community
Advanced