blueprint-derive-prd
Installation
SKILL.md
Generate a Product Requirements Document (PRD) for an existing project by analyzing README, documentation, and project structure.
When to Use This Skill
| Use this skill when... | Use blueprint-derive-adr instead when... |
|---|---|
| You're onboarding an existing project and need a PRD from README/docs | You want architectural decisions documented as ADRs, not requirements |
| You need to extract problem statements, stakeholders, personas from existing prose | Use blueprint-derive-plans instead to derive PRDs+ADRs+PRPs together |
| You want to capture features and user goals retroactively | Use blueprint-init instead when you need to bootstrap blueprint first |
Use Case: Onboarding existing projects to Blueprint Development system.
Prerequisites:
- Blueprint Development initialized (
docs/blueprint/exists) - Project has some existing documentation (README.md, docs/, etc.)
Steps: