planning-stories

What problem does it solve?

This Skill turns a validated PRD and system architecture into a structured set of user story outlines, so execution agents can implement features without ambiguous scope, missing dependencies, or duplicated contract definitions.

Core Features & Use Cases

• Story Decomposition with Guardrails: Breaks each PRD user story group into right-sized stories (bounded for ~30–60 minutes) while enforcing strict “WHEN / WHEN NOT to use” rules to prevent premature or out-of-scope work.
• Dependency Manifest + Integration Strategy: Produces per-story dependency manifests and an integration strategy that records mocks vs real connections and ensures every mock is realized later or explicitly deferred.
• Shared Contract Identification: Detects shared interfaces (data shapes, API contracts, auth models, error formats), extracts them into plan/contracts/, and connects stories to provided/consumed contracts.
• Folder Structure Output: Creates plan/user-stories/US-NNN-name/ folders with story.md files and adds plan/contracts/ entries for identified shared contracts.

Quick Start

Use planning-stories to decompose plan/prd.md and plan/system-architecture.md into plan/user-stories/ story folders after the Planning Hub validates the PRD and architecture inputs.