shai-story-decomposition

To break down features into actionable user stories, decompose each feature into individual stories with 2-3 BDD acceptance criteria. This ensures clear, testable requirements that enable faster sprint planning and reliable delivery.

The best way to write user stories for sprint planning is generating individual story files with concise statements and 2-3 BDD scenarios. This structured approach provides clear, testable acceptance criteria for reliable development.

You can use a standalone feature description to generate user stories. The decomposition process applies to both standalone feature descriptions and outputs from a feature-mapping workflow, creating individual story files with BDD acceptance criteria.

To save user stories for task breakdown workflows, generate each story as a {brief-name}.story.md file under the docs/stories directory. These files include YAML frontmatter for loading into the task breakdown workflow.

Each user story should have 2-3 acceptance criteria when decomposing features. These are structured as BDD scenarios to ensure the stories are testable and ready for implementation in the next development sprint.

Yes, this story decomposition approach provides a repeatable workflow linking feature-mapping, story writing, and task breakdown. It generates story files with YAML frontmatter designed specifically for loading into downstream task breakdown workflows.