User Story Documents

Skill Name: user-story-writing

Background & Use Cases

The requirements specification describes "what the system should do," but the development team needs to know "what should I implement in this iteration and what counts as done." Throwing large chunks of requirements directly at developers leaves them not knowing where to start. This skill breaks requirements down into user story cards that developers can directly execute — each story is an independently verifiable functional unit.

Input & Output

You need to provide: A confirmed requirements specification (scenario list + scenario deep-dive tables).

You will receive: A user story collection containing: story cards in As-I-Want-So-That format, Given-When-Then acceptance criteria, a story map organized by user activities, and story priority ranking.

Process Overview

The Agent decomposes each scenario in the PRD into user story cards: first a one-sentence description in "As a [role], I want [goal], so that [benefit]" format, then Given-When-Then acceptance criteria. After all stories are written, they are arranged into a story map by user activity and annotated with priorities. In the MVP phase, you confirm 8-15 key stories first; remaining stories are added in subsequent iterations.

flowchart TD s0["Story Decomposition Preparation"] s1["Single Scenario Story-by-Story Progression"] s2["Single Scenario Consistency Check & Close-Out"] s3["Story Map by User Activity Column Progression"] s4["Story Map Overall Close-Out"] s5["Priority Definition & Traceability Relationship Setup"] s6["Validation & Confirmation"] s7["Document Integration: Metadata + Story Decomposition Preparation"] s8["Document Integration: User Story Collection"] s9["Document Integration: Story Map + Priority & Traceability"] s10["Document Integration: Validation Checklist + Pending Clarifications + Finalization Statement"] s0 --> s1 s1 --> s2 s2 --> s3 s3 --> s4 s4 --> s5 s5 --> s6 s6 --> s7 s7 --> s8 s8 --> s9 s9 --> s10