blueprint-derive-adrlisted

Generate Architecture Decision Records (ADRs) for an existing project by analyzing code structure, dependencies, and documentation. ## When to Use This Skill | Use this skill when... | Use blueprint-derive-prd instead when... | |---|---| | You're documenting implicit architecture decisions retroactively from code | You want to extract requirements/personas from README, not decisions | | You need to capture framework, database, state-management choices as ADRs | Use blueprint-derive-plans instead to derive PRDs+ADRs+PRPs together | | You're onboarding an existing project and want decisions on record | Use adr-relationships instead when authoring/validating one ADR | **Use Case**: Onboarding existing projects to Blueprint Development system, documenting implicit architecture decisions. **Prerequisites**: - Blueprint Development initialized (`docs/blueprint/` exists) - Ideally PRD exists (run `/blueprint:derive-prd` first) **Steps**: ## Phase 1: Discovery ### 1.1 Check Prerequisites ```bash ls docs/blueprint/manifest.json ls docs/prds/ ``` If blueprint not initialized → suggest `/blueprint:init` If no PRD → suggest `/blueprint:derive-prd` first (recommended, not required) ### 1.2 Create ADR Directory ADRs live at the **top level** under `docs/adrs/` — not `docs/blueprint/adrs/`. This matches `/blueprint:init`'s canonical layout and the `document-management-rule.md` template. Never write ADRs under `docs/blueprint/`; that path is reserved for blueprint machinery. ```bas