decompose-requirement

To break down an epic into user stories, you decompose the high-level requirement into sequenced child items using vertical slicing. This process outputs a summary table and detailed markdown for each story with user stories and acceptance criteria.

Vertical slicing in requirement decomposition is a technique that enforces the creation of child items delivering independent user value across all layers. It ensures that decomposed stories or subtasks are manageable, well-sequenced, and provide standalone functionality.

Subtasks are prioritized by sequencing child items based on their dependencies, risk, value, and learning opportunities. This ordering ensures efficient workflow and clarity when breaking down a large requirement into manageable actions.

Yes, you can automatically generate acceptance criteria for user stories during requirement breakdown. The decomposition process outputs detailed markdown for each child item, explicitly including user stories and their corresponding acceptance criteria.

The best way to split a large user story into subtasks is to decompose it using vertical slicing to ensure independent value delivery. The resulting subtasks are sequenced by dependencies, risk, and value to maintain an efficient agile workflow.