blueprint-adr-list

List Architecture Decision Records dynamically from the filesystem. ## When to Use This Skill | Use this skill when... | Use blueprint-docs-list instead when... | |---|---| | You only need ADR-specific output with title, status, date, domain | You want a combined index across ADRs, PRDs, and PRPs | | You're generating an ADR index for a README | You want quick counts/summaries of all blueprint document types | | You're auditing ADR status in a markdown table | Use blueprint-adr-validate instead for relationship/conflict checks | **Use Case**: Generate ADR index tables for README files, audit ADR status, or quickly view all architectural decisions. **Steps**: ## 1. Check for ADRs ```bash ls docs/adrs/*.md 2>/dev/null | head -1 ``` If no ADRs found: ``` No ADRs found in docs/adrs/ Run `/blueprint:derive-plans` to generate ADRs from project analysis. ``` ## 2. Generate ADR Table ADR formats vary: some use markdown headers (`## Status`, `## Date`), others use YAML frontmatter (`status:`, `date:`). The extraction handles both. **Command to generate markdown table**: ```bash printf "| ADR | Title | Status | Date |\n|-----|-------|--------|------|\n" && \ fd '^[0-9]{4}-.*\.md$' docs/adrs -x awk ' # Extract title from H1 header /^# ADR-/ {gsub(/^# ADR-[0-9]+: /, ""); title=$0} # Extract status from ## Status section (next non-empty line) /^## Status/ {p_status=1; next} p_status && NF {status=$0; p_status=0} # Extract date from ## Date section (next non-empty ...