blueprint-plugin/skills/blueprint-docs-list/SKILL.md
List blueprint documents (ADRs, PRDs, PRPs) with frontmatter metadata. Use when listing docs, auditing statuses, or generating an index for project documentation.
npx skillsauth add laurigates/claude-plugins blueprint-docs-listInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
List blueprint documents programmatically from the filesystem. Extracts metadata from YAML frontmatter and markdown headers.
| 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.
| Arg | Description |
|-----|-------------|
| adrs | List Architecture Decision Records |
| prds | List Product Requirements Documents |
| prps | List Product Requirement Prompts |
| all | Summary of all document types |
adrsRun /blueprint:adr-list — it handles ADR-specific extraction with both header-section and frontmatter support.
prdsprintf "| 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 "$f" | grep -m1 "^title:" | sed 's/^title:[[:space:]]*//' || true)
doc_status=$(head -50 "$f" | grep -m1 "^status:" | sed 's/^status:[[:space:]]*//' || true)
doc_date=$(head -50 "$f" | grep -m1 "^date:\|^created:" | sed 's/^[^:]*:[[:space:]]*//' || true)
# Fallback: extract title from H1
if [ -z "$doc_title" ]; then
doc_title=$(head -20 "$f" | grep -m1 "^# " | sed 's/^# //')
fi
printf "| [%s](%s) | %s | %s | %s |\n" \
"${fname%.md}" "$f" "${doc_title:-(untitled)}" "${doc_status:--}" "${doc_date:--}"
done
prpsprintf "| PRP | Title | Status | Confidence |\n|-----|-------|--------|------------|\n" && \
for f in docs/prps/*.md; do
[ -f "$f" ] || continue
fname=$(basename "$f")
[ "$fname" = "README.md" ] && continue
doc_title=$(head -50 "$f" | grep -m1 "^title:" | sed 's/^title:[[:space:]]*//' || true)
doc_status=$(head -50 "$f" | grep -m1 "^status:" | sed 's/^status:[[:space:]]*//' || true)
doc_confidence=$(head -50 "$f" | grep -m1 "^confidence:" | sed 's/^confidence:[[:space:]]*//' || true)
if [ -z "$doc_title" ]; then
doc_title=$(head -20 "$f" | grep -m1 "^# " | sed 's/^# //')
fi
printf "| [%s](%s) | %s | %s | %s |\n" \
"${fname%.md}" "$f" "${doc_title:-(untitled)}" "${doc_status:--}" "${doc_confidence:--}"
done
allShow counts and status breakdown for each document type:
echo "## Blueprint Documents Summary"
echo ""
for doc_type in adrs prds prps; do
doc_count=$(ls docs/$doc_type/*.md 2>/dev/null | grep -cv 'README.md' || echo 0)
echo "### ${doc_type^^}: $doc_count documents"
if [ "$doc_count" -gt 0 ]; then
for s in Accepted Proposed Deprecated Superseded draft ready approved; do
sc=$(grep -ril "^status:.*$s\|^$s$" docs/$doc_type/*.md 2>/dev/null | wc -l | tr -d ' ')
[ "$sc" -gt 0 ] && echo "- $s: $sc"
done
fi
echo ""
done
After listing, suggest:
/blueprint:derive-plans to generate documents"testing
Verify accumulated bug claims at upstream HEAD and dedup against trackers before filing issues. Use when filing upstream reports from backlogs, audit docs, or git-history findings.
documentation
Gate outward-bound text (upstream issues, docs, PR bodies) through isolated haiku fresh-reader critique before publishing. Use when an artifact must survive a reader with zero project context.
tools
Suggest improvements to SKILL.md content, descriptions, or tool config from eval results. Use when raising pass rates, fixing triggering, or iterating on a skill after evaluation.
tools
deadbranch CLI for stale-branch cleanup — dry-run preview, TUI or non-interactive delete, protects main/develop/WIP. Use when asked to clean up branches, prune branches, or remove stale branches.