prd-generationlisted

# PRD Generation Skill ## What Is a PRD? A Product Requirements Document (PRD) is the central artifact that bridges product strategy and engineering execution. It captures the why, what, and how of a product initiative so that every stakeholder -- from designers and engineers to leadership and QA -- operates from a single source of truth. A well-written PRD reduces ambiguity, prevents scope creep, and provides a measurable framework against which the team can evaluate success. Within the product development lifecycle a PRD typically sits between the discovery phase (where problems are identified and validated) and the design/engineering phase (where solutions are built). It is not a static document; it evolves through drafts, reviews, and revisions as the team's understanding deepens. This skill treats the PRD as a living document and structures it accordingly. ## Five-Step Workflow Every PRD generated by this skill follows a disciplined five-step process. Each step must be completed before moving to the next. ### Step 1 -- Understand Context Before writing a single line, scan the project to build situational awareness. @../shared/project-context.md Execute the Project Context Protocol (PC.1 through PC.3) to determine: 1. **Project structure and existing documentation** (PC.1) 2. **Tech stack and framework** (PC.2) 3. **Project profile** (PC.3) — Web API, CLI Tool, Frontend, etc. Additionally: 4. **Scan the `docs/` directory** (if it exists) to find prior PRDs, tech