Introduction
This skill breaks a validated user problem or product requirement into stories that can be discussed, implemented, and accepted independently. Each story includes role, goal, value, Given-When-Then scenarios, edge cases, dependencies, and risks. Oversized stories are split by flow, rule, or data boundary. User value, technical tasks, and discovery work remain distinct so internal implementation is not disguised as a user story.
Use Cases
Use it for refinement, backlog preparation, iteration planning, and cross-functional review, or to audit existing stories for missing value and testability while aligning product, design, engineering, and QA.
Template
Provide the user problem, target user, flow, business rules, scope, dependencies, and success criteria. The output includes stories, acceptance scenarios, edge cases, splitting guidance, dependencies, and open questions.
