| created | "2026-02-06T00:00:00.000Z" |
| modified | "2026-05-09T00:00:00.000Z" |
| reviewed | "2026-04-25T00:00:00.000Z" |
| description | List blueprint documents (ADRs, PRDs, PRPs) with frontmatter metadata. Use when listing docs, auditing statuses, or generating an index for project documentation. |
| args | <type> |
| allowed-tools | Bash, Glob |
| model | sonnet |
| argument-hint | adrs | prds | prps | all |
| name | blueprint-docs-list |
List blueprint documents programmatically from the filesystem. Extracts metadata from YAML frontmatter and markdown headers.
When to Use This Skill
| Use this skill when... | Use blueprint-adr-list instead when... |
|---|
| You want a combined index of ADRs, PRDs, and PRPs (or summary across all) | You only need an ADR-specific index table |
| You want to audit document statuses across all blueprint types | You need ADR-specific fields like domain or status filtering |
You want a quick overview using all to see counts of every doc type | You're generating an ADR index for a README |
Use Case: Audit document status, generate index tables, or get a quick overview of all project documentation.
Parameters
| Arg | Description |
|---|
adrs | List Architecture Decision Records |
prds | List Product Requirements Documents |
prps | List Product Requirement Prompts |
all | Summary of all document types |
Execution
If arg is adrs
Run /blueprint:adr-list — it handles ADR-specific extraction with both header-section and frontmatter support.
If arg is prds
printf "| PRD | Title | Status | Date |\n|-----|-------|--------|------|\n" && \
for f in docs/prds/*.md; do
[ -f "$f" ] || continue
fname=$(basename "$f")
[ "$fname" = "README.md" ] && continue
doc_title=$(head -50 "" | grep -m1 | sed || )
doc_status=$( -50 | grep -m1 | sed || )
doc_date=$( -50 | grep -m1 | sed || )
[ -z ];
doc_title=$( -20 | grep -m1 | sed )
\
