story-split

To split large user stories into smaller agile deliverables, apply the eight splitting patterns to isolate independent, value-delivering increments from complex acceptance criteria. This ensures each resulting story remains manageable and independently shippable.

The best way to break down a user story with multiple Gherkin scenarios is to analyze the individual scenario paths and apply story-splitting patterns to separate them into distinct, independent user stories. Each split story retains its specific Gherkin acceptance criteria.

To validate if split user stories meet agile INVEST criteria, enforce the INVEST checks (Independent, Negotiable, Valuable, Estimable, Small, Testable) on each generated story. This ensures every divided story delivers standalone value and remains viable for development.

To generate markdown documentation for split user stories in agile projects, output each divided story as a separate markdown file following a canonical story-gherkin template. These files are automatically saved under the docs/specs/stories/ directory structure.

Yes, you can use story-splitting patterns on user stories with complex acceptance criteria. The process specifically handles complex acceptance criteria by transforming them into multiple smaller, manageable stories that each deliver value and comply with the canonical template.