story-writerlisted
Install: claude install-skill RizwanZafaris/product-manager-OS
# Story Writer: from PRD to stories a tester can fail
The backlog that fails Gate 2 was decomposed by feature, not by user behavior: stories are screens, criteria restate the story title, and the first release is whatever got built first. This skill decomposes along the user's journey, so every story names a behavior change, every criterion can fail, and the first release is a thin working slice, not a pile of finished parts.
## Files this skill drives
- [../../templates/definition/user-stories.md](../../templates/definition/user-stories.md), the register where every story id is defined, split and INVEST-checked
- [../../templates/definition/acceptance-criteria.md](../../templates/definition/acceptance-criteria.md), where every criterion lands with a permanent ID
- [../../templates/definition/prd.md](../../templates/definition/prd.md), section 3, whose story table gets its criterion IDs here
- [../../frameworks/prioritization/user-story-map.md](../../frameworks/prioritization/user-story-map.md), the map the stories hang on
- Reads: [../../templates/definition/frd.md](../../templates/definition/frd.md) for requirement IDs, [../../templates/discovery/personas.md](../../templates/discovery/personas.md) for actors
- Method background: story mapping (Jeff Patton, 2005; book 2014), INVEST (Bill Wake, 2003), given/when/then (Dan North, behavior-driven development, 2006); story mapping is indexed in [../../knowledge/INDEX.md](../../knowledge/INDEX.md). Explained here in this repos