blueprint-adr-validate

# /blueprint:adr-validate Validate Architecture Decision Records for relationship consistency, reference integrity, and domain conflicts. **Usage**: `/blueprint:adr-validate [--report-only]` ## When to Use This Skill | Use this skill when... | Use alternative when... | |------------------------|-------------------------| | Maintaining ADR integrity before releases | Creating new ADRs (use `/blueprint:derive-plans`) | | Auditing after refactoring or changes | Quick one-time documentation review | | Regular documentation review process | General ADR reading | ## Context - ADR directory exists: !`find . -path '*/docs/adrs' -maxdepth 2 -type d` - ADR count: !`find . -path '*/docs/adrs/*' -name "*.md" -type f` - Domain-tagged ADRs: !`find . -path '*/docs/adrs/*' -maxdepth 3 -name '*.md' -exec grep -l "^domain:" {} +` - Flag: !`echo "${1:---}"` ## Parameters Parse `$ARGUMENTS`: - `--report-only`: Output validation report without prompting for fixes - Default: Interactive mode with remediation options ## Execution Execute complete ADR validation and remediation workflow: ### Step 1: Discover all ADRs 1. Check for ADR directory at `docs/adrs/` 2. If missing → Error: "No ADRs found in docs/adrs/" 3. Parse all ADR files: `ls docs/adrs/*.md` 4. Extract frontmatter for each ADR: number, date, status, domain, supersedes, superseded_by, extends, related ### Step 2: Validate reference integrity For each ADR, validate: 1. **supersedes references**: Verify target exists, tar...