write-user-stories

To write agile user stories from a vague product brief, the skill converts the input into a narrative-driven walking skeleton and formats stories as "As a [user], I want [goal], so that [benefit]" with Given/When/Then acceptance criteria. This process produces backlog-ready items for sprint planning.

A walking skeleton in agile story mapping is a narrative spine that covers the full product flow end-to-end. It slices user stories into incremental releases and tracks dependencies to sequence delivery, ensuring that each release provides a measurable, functional slice of the product.

To define Given/When/Then acceptance criteria for edge cases, the skill applies this structure to both happy paths and boundary conditions within user stories. This ensures that narrative-driven product briefs yield measurable, testable criteria for backlog-ready agile story mapping.

Yes, you can use story mapping to slice user stories into releases and track dependencies. The skill processes strategy documents and feature ideas to surface sequencing constraints, guiding incremental delivery planning by mapping out the walking skeleton across sprints.

The best way to structure backlog-ready user stories for sprint planning is to build a narrative spine from the product journey. This approach formats headlines as user goals and defines Given/When/Then acceptance criteria to ensure measurable outcomes before release slicing.