blueprint-derive-prdlisted

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**: ## Phase 1: Discovery ### 1.1 Check Prerequisites ```bash ls docs/blueprint/manifest.json ``` If not found → suggest running `/blueprint:init` first. ### 1.2 Gather Project Documentation Search for existing documentation: ```bash fd -e md -d 3 . | head -20 ``` Key files to look for: - `README.md` - Primary project description - `docs/` - Documentation directory - `CONTRIBUTING.md` - Contribution guidelines - `ARCHITECTURE.md` - Architecture overview - `package.json` / `pyproject.toml` / `Cargo.toml` - Project metadata ### 1.3 Read Primary Documentation Read and analyze: - R