What problem does it solve? Turning rough feature ideas into a formal Product Requirements Document is time-consuming, and PRDs often miss critical elements like success metrics, dependencies, and risk assessment, leading to misalignment before engineering starts. ## Core Features & Use Cases - Context-Aware Drafting: Reads your existing context files (product.md, personas.md, company.md, competitors.md) to ground the PRD in what is already known about your product and users. - Structured PRD Template: Produces a complete PRD covering problem statement, evidence, lagging and leading success indicators, user stories, non-goals, dependencies with critical path, and a sign-off checklist. - Risk Assessment: Applies Marty Cagan's Value/Usability/Feasibility/Viability framework to surface risks before building, plus open questions paired with validation experiments. - Use Case: You have a feature idea discussed only in meetings. Provide the problem description and any evidence, and receive a stakeholder-ready PRD with placeholders flagged where real metrics are still needed. ## Quick Start Ask the assistant to write a PRD for your feature idea, describing the problem, who experiences it, and any evidence you have.
