blueprint-statuslisted

Display the current blueprint configuration status with three-layer architecture breakdown. ## When to Use This Skill | Use this skill when... | Use blueprint-execute instead when... | |---|---| | You want a read-only status report (PRD/ADR/PRP counts, traceability) | You want auto-detection that takes the next action, not just reports | | You want the three-layer architecture breakdown | Use blueprint-feature-tracker-status instead for FR/phase progress | | You want to audit orphan docs and stale generated content | Use blueprint-sync instead for an actionable drift reconcile | | You run with `--report-only` for non-interactive auditing | Use blueprint-upgrade instead when you've already spotted an upgrade | ## Flags | Flag | Description | |------|-------------| | `--report-only` | Display status report and exit without prompting for next action | ## Steps 1. **Check if blueprint is initialized**: - Look for `docs/blueprint/manifest.json` - If not found, report: ``` Blueprint not initialized in this project. Run `/blueprint:init` to get started. ``` 2. **Read manifest and gather information**: - Parse `manifest.json` for version and configuration - Parse `id_registry` for traceability metrics - Count PRDs in `docs/prds/` - Count ADRs in `docs/adrs/` - Count PRPs in `docs/prps/` - For ADRs, also count: - With domain tags (`grep -l "^domain:" docs/adrs/*.md | wc -l`) - With relationship declarations (supersedes, exte