What problem does it solve? Turning a validated app idea into structured, per-feature Product Requirements Documents is slow and inconsistent when done by hand. This Skill automates the decomposition of an idea brief into 4–8 feature PRDs with nested screen definitions, a Mermaid navigation graph, and a master index. ## Core Features & Use Cases - Feature Decomposition: Reads idea-brief.md feature seeds and proposes 4–8 features grouped into five fixed user-journey buckets (Acquisition, Activation, Core Loop, Retention, Settings), with a hard cap of 8 and monetization explicitly out of scope. - Per-Feature PRD Generation: Writes one markdown PRD per feature using a strict template covering user stories, screens, functional and non-functional requirements, data needs, analytics events, and out-of-scope items, with sensible pre-filled defaults. - Cross-Feature Review: Generates a Mermaid navigation graph, detects shared components and naming conflicts, and writes a master INDEX.md. - Use Case: After validating an app idea with the idea pipeline, run this Skill to produce a complete plans/{slug}/prd/ directory of feature PRDs ready to hand off to a design-spec stage. ## Quick Start Ask the AI to decompose the validated idea brief in plans/{slug}/idea-brief.md into per-feature PRDs with screen lists and a navigation graph.