planning-stories

To decompose a PRD into implementable user stories, you need a validated PRD and system architecture to generate bounded story outlines with dependency manifests, shared contract identification, and folder structure outputs.

Shared contract extraction in user story planning identifies shared interfaces like API contracts and data shapes, extracts them into a shared registry format under `plan/contracts/`, and connects stories to provided or consumed contracts.

To prevent circular dependencies when breaking down system architecture into stories, apply ordering validation during story decomposition to detect boundary misalignment and ensure per-story dependency manifests enforce correct execution sequencing.

Yes, you need a validated PRD before generating user story outlines because strict PRD and architecture validation gating is required to prevent premature or out-of-scope work during Phase 2 story decomposition.

Mock and realize integration strategies in story decomposition record mock versus real connections per story, ensuring every mock is either realized later or explicitly deferred to maintain integration consistency across user stories.

The best way to structure user stories for execution agents is creating `plan/user-stories/US-NNN-name/` folders with `story.md` files, bounding stories to 30–60 minutes of work with explicit dependency manifests to eliminate ambiguous scope.