What problem does it solve? Turning a raw product idea into a validated PRD and buildable backlog usually means ad-hoc discovery, skipped validation, and documents that cannot be resumed or audited. This Skill enforces a disciplined six-phase sequence where every phase produces versioned markdown artifacts and must pass an explicit human gate before the next begins. ## Core Features & Use Cases - Six-phase orchestration: Sequences nineteen bundled sub-skills across Framing, Discovery, Requirements and Validation, PRD, Delivery Planning, and a closing Strategy Session, carrying each phase's artifacts forward as the next phase's input. - Auditable state and gates: Maintains an INDEX.md state file, a MEASUREMENT.md metrics thread (baseline, target, instrument, read-out date), and recorded gate pass/fail decisions so work can resume and failures stay visible. - Anti-hallucination guardrails: Forbids invented market figures, user quotes, estimates, and approvals; unsourced values are labelled as assumptions or placeholders. - Use Case: A PM with a rough idea for an in-app feature runs the full flow and ends with POSITIONING.md, a validated PROBLEM_STATEMENT.md, a PRD, an epic breakdown with board_import.csv, and a roadmap ready to push to Jira or Linear. ## Quick Start Ask the assistant to onboard your new product idea end to end, describing the product, the company, and the primary user in a couple of sentences.
