What problem does it solve? Turning a rough feature idea into a complete Product Requirements Document often means guessing at scope, personas, and success metrics. This Skill replaces guessing with an evidence-grounded interview process that explores existing code and prior PRDs before asking batched questions, then writes a PRD from a consistent template. ## Core Features & Use Cases - Batched stakeholder interview: Asks 3-5 grounded questions per round covering personas, scope, dependencies, entitlements, edge cases, and success metrics, each with concrete options and an explicit defer escape hatch. - Prior-art exploration: Reads the README, product vision, sibling PRDs, and referenced repositories to answer questions from code before leaving them open. - Open-question classification: Separates genuinely unanswerable items into engineering spikes or product decisions while folding resolved answers into an audit trail. - Use Case: A product owner describes a game-verification feature for the mahjong club site; the Skill interviews them about scope and access control, checks existing PRDs for prerequisites, then produces a complete PRD with acceptance criteria and success metrics. ## Quick Start Ask the assistant to author a PRD for your feature idea, describing what it is, why it is needed, and what problem it solves.
