Does resizing a story affect project dependencies?

Yes, the skill includes a specific step to analyze and update the dependency map, ensuring that the new, smaller stories are sequenced correctly to unblock other team members.

How does the skill determine where to split a story?

It looks for natural boundaries such as CRUD operations, frontend vs. backend separation, happy path vs. error handling, and MVP vs. enhancement phases.

When should I use the Resize Story skill?

Use this skill whenever a story is estimated to take more than 3 days (24 hours) to complete, or when a task is so small (under 4 hours) that it creates unnecessary management overhead.

What is the PROBE method mentioned in the skill?

PROBE (Proxy Based Estimation) is a structured technique used within the PSP framework to provide highly accurate time and size estimates based on historical data and similar past tasks.

Story Resizer & Estimation Optimizer

Name: Story Resizer & Estimation Optimizer
Author: resolve-io

byresolve-io

•

생산성 및 워크플로

Optimizes software development workflows by intelligently splitting or combining user stories based on complexity and time estimates.

소개

The Resize Story skill is a specialized PRISM framework tool designed to maintain predictable development cycles by ensuring every task is 'right-sized.' It automatically analyzes user stories to identify those that are too large (exceeding 3 days) or too small (under 0.5 days), providing structured recommendations for splitting or combining them. By leveraging the PROBE estimation method and identifying natural architectural boundaries, this skill helps teams reduce risk, maintain continuous flow, and ensure that every development unit is independently testable and valuable.

주요 기능

Intelligent splitting across functional, technical, and temporal boundaries
Automated story size assessment against 4-24 hour target windows
PROBE-based re-estimation for improved historical accuracy
1 GitHub stars
Candidate identification for combining micro-tasks to reduce overhead
Comprehensive resize reporting with dependency impact analysis

사용 사례

Combining related configuration or minor UI changes into cohesive tasks
Refining 'monster' stories during sprint planning to fit into 3-day windows
Updating story scope and estimates when new technical complexity is discovered

소개

주요 기능

Intelligent splitting across functional, technical, and temporal boundaries
Automated story size assessment against 4-24 hour target windows
PROBE-based re-estimation for improved historical accuracy
1 GitHub stars
Candidate identification for combining micro-tasks to reduce overhead
Comprehensive resize reporting with dependency impact analysis

사용 사례

Combining related configuration or minor UI changes into cohesive tasks
Refining 'monster' stories during sprint planning to fit into 3-day windows
Updating story scope and estimates when new technical complexity is discovered