What problem does it solve? Turning a vague feature idea into a concrete, actionable product requirements document is hard—ambiguities get missed, scope creeps, and implementation teams lack clear guidance. This Skill interviews you, explores your codebase, and produces a well-structured PRD saved as a local artifact. ## Core Features & Use Cases - Guided Requirements Interview: Asks focused, high-signal questions about the problem, users, goals, constraints, and out-of-scope items. - Codebase-Aware Scoping: Inspects existing modules, terminology, and integration constraints so the PRD reflects real system boundaries. - Standardized PRD Output: Writes a structured prd.md (Summary, Problem, Goals, Non-Goals, Requirements, User Flows, Success Criteria, Risks, Open Questions) under a dedicated .prd/<slug>/ folder with reserved issues/, plans/, and rfcs/ subfolders. - Use Case: You want to add a notifications feature to your app. The Skill asks targeted questions, reviews relevant code, then produces .prd/notifications/prd.md ready for planning and implementation. ## Quick Start Ask the assistant to write a PRD for your feature idea, for example: "Help me write a PRD for adding team workspaces to our app."
