What problem does it solve? Turning an approved design into a structured plan of record is where ambiguity creeps in: requirements get written as vague wishes, phases become filler, and downstream agents or reviewers receive documents they cannot act on. This Skill produces PRDs written as work orders for strangers — every requirement falsifiable, every phase independently shippable, every open question owned. ## Core Features & Use Cases - Phased PRD authoring: Generates a PRD with a fixed structure (problem, goal, non-goals, decisions, phases, open questions) where each phase ships something verifiable on its own and passes a cancellation test. - Falsifiable acceptance criteria: Enforces atomic, testable, implementation-free criteria per phase, including testing and documentation expectations that are never deferred to a later phase. - Task decomposition: After user approval, converts phases into backlog tasks (via a Backlog.md MCP when available, or a markdown task breakdown otherwise) with verbatim criteria and recorded dependencies. - Use Case: After brainstorming and grilling have settled the design for a new feature, invoke this Skill to produce a dated PRD in docs/prd/, get it approved, and create one task per phase ready for implementation planning. ## Quick Start Ask the agent to write the PRD for the approved design from the brainstorming session and break it into tasks.
