Show blueprint version, configuration, and check for available upgrades
Scanned 2/12/2026
Install via CLI
openskills install laurigates/claude-plugins---
model: opus
created: 2025-12-17
modified: 2026-02-07
reviewed: 2025-12-22
description: "Show blueprint version, configuration, and check for available upgrades"
args: "[--report-only]"
argument-hint: "--report-only to display status without interactive prompts"
allowed-tools: Read, Bash, Glob, AskUserQuestion
name: blueprint-status
---
Display the current blueprint configuration status with three-layer architecture breakdown.
## 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, extends, related)
- By status (Accepted, Superseded, Deprecated)
- Count work-orders (pending, completed, archived)
- Count generated rules in `.claude/rules/`
- Count custom skills in `.claude/skills/`
- Count custom commands in `.claude/commands/`
- Check for `.claude/rules/` directory
- Check for `CLAUDE.md` file
- Check for `docs/blueprint/feature-tracker.json`
- If feature tracker exists, read statistics and last_updated
3. **Check for upgrade availability**:
- Compare `format_version` in manifest with current plugin version
- Current format version: **3.0.0**
- If manifest version < current → upgrade available
4. **Check generated content status**:
- For each generated rule in manifest:
- Hash current file content
- Compare with stored `content_hash`
- Status: `current` (unchanged), `modified` (user edited), `stale` (source PRDs changed)
5. **Display status report**:
```
Blueprint Status
Version: v{format_version} {upgrade_indicator}
Initialized: {created_at}
Last Updated: {updated_at}
Project Configuration:
- Name: {project.name}
- Type: {project.type}
- Stack: {project.detected_stack}
- Rules Mode: {structure.claude_md_mode}
Project Documentation (docs/):
- PRDs: {count} in docs/prds/
- ADRs: {count} in docs/adrs/
- With domain tags: {count}/{total} ({percent}%)
- With relationships: {count}
- Status: {accepted} Accepted, {superseded} Superseded, {deprecated} Deprecated
- PRPs: {count} in docs/prps/
Work Orders (docs/blueprint/work-orders/):
- Pending: {count}
- Completed: {count}
- Archived: {count}
Three-Layer Architecture:
Layer 1: Plugin (blueprint-plugin)
- Commands: /blueprint:* (auto-updated with plugin)
- Skills: blueprint-development, blueprint-migration, confidence-scoring
- Agents: requirements-documentation, architecture-decisions, prp-preparation
Layer 2: Generated (.claude/rules/)
- Rules: {count} ({status_summary})
{list each with status indicator: ✅ current, ⚠️ modified, 🔄 stale}
Layer 3: Custom (.claude/skills/, .claude/commands/)
- Skills: {count} (user-maintained)
- Commands: {count} (user-maintained)
{If feature_tracker enabled:}
Feature Tracker:
- Status: Enabled
- Source: {feature_tracker.source_document}
- Progress: {statistics.complete}/{statistics.total_features} ({statistics.completion_percentage}%)
- Last Sync: {last_updated}
- Phases: {count in_progress} active, {count complete} complete
Traceability (ID Registry):
- Total documents: {count} ({x} PRDs, {y} ADRs, {z} PRPs, {w} WOs)
- With IDs: {count}/{total} ({percent}%)
- Linked to GitHub: {count}/{total} ({percent}%)
- Orphan documents: {count} (docs without GitHub issues)
- Orphan issues: {count} (issues without linked docs)
- Broken links: {count}
{If orphans exist:}
Orphan Documents (no GitHub issues):
- {PRD-001}: {title}
- {PRP-003}: {title}
Orphan GitHub Issues (no linked docs):
- #{N}: {title}
- #{M}: {title}
Structure:
✅ docs/blueprint/manifest.json
{✅|❌} docs/prds/
{✅|❌} docs/adrs/
{✅|❌} docs/prps/
{✅|❌} docs/blueprint/work-orders/
{✅|❌} docs/blueprint/ai_docs/
{✅|❌} docs/blueprint/feature-tracker.json
{✅|❌} .claude/rules/
{✅|❌} CLAUDE.md
{If upgrade available:}
Upgrade available: v{current} → v{latest}
Run `/blueprint:upgrade` to upgrade.
{If modified generated content:}
Modified content detected: {count} files
Run `/blueprint:sync` to review changes.
Run `/blueprint:promote [name]` to move to custom layer.
{If stale generated content:}
Stale content detected: {count} files (PRDs changed since generation)
Run `/blueprint:generate-skills` to regenerate.
{If up to date:}
Blueprint is up to date.
```
6. **Additional checks**:
- Warn if feature-tracker.json is stale (> 1 day since last update)
- Warn if PRDs exist but no generated rules
- Warn if modular rules enabled but `.claude/rules/` is empty
- Warn if generated content is modified or stale
- Warn if feature-tracker.json is older than 7 days (needs sync)
- Warn if TODO.md has been modified since last sync
- Warn if ADRs have potential issues:
- Multiple "Accepted" ADRs in same domain (potential conflict)
- ADRs without domain tags (harder to detect conflicts)
- Missing bidirectional links (e.g., supersedes without corresponding superseded_by)
- **Traceability checks**:
- Warn if documents exist without IDs (run `/blueprint:sync-ids`)
- Warn if orphan documents exist (docs without GitHub issues)
- Warn if orphan issues exist (GitHub issues without linked docs)
- Warn if broken links detected (referenced docs/issues don't exist)
7. **If `--report-only`**: Output the status report from Steps 5-6 and exit. Skip the interactive prompt below.
8. **Prompt for next action** (use AskUserQuestion):
**Build options dynamically based on state:**
- If upgrade available → Include "Upgrade to v{latest}"
- If modified content → Include "Sync generated content"
- If stale content → Include "Regenerate skills"
- If PRDs exist but no generated skills → Include "Generate skills from PRDs"
- If skills exist but no commands → Include "Generate workflow commands"
- If CLAUDE.md stale → Include "Update CLAUDE.md"
- If feature tracker exists but stale → Include "Sync feature tracker"
- If ADRs have potential issues → Include "Validate ADRs"
- If documents without IDs → Include "Sync document IDs"
- If orphan documents/issues → Include "Link documents to GitHub"
- Always include "Continue development" and "I'm done"
```
question: "What would you like to do?"
options:
# Dynamic - include based on state detected above
- label: "Upgrade to v{latest}" (if upgrade available)
description: "Upgrade blueprint format to latest version"
- label: "Sync generated content" (if modified)
description: "Review changes to generated skills/commands"
- label: "Regenerate from PRDs" (if stale)
description: "Update generated content from changed PRDs"
- label: "Generate rules from PRDs" (if PRDs exist, no rules)
description: "Extract project-specific rules from your PRDs"
- label: "Update CLAUDE.md" (if stale or missing)
description: "Regenerate project overview document"
- label: "Sync feature tracker" (if feature tracker stale)
description: "Synchronize tracker with TODO.md"
- label: "Validate ADRs" (if ADR issues detected)
description: "Check ADR relationships, conflicts, and missing links"
- label: "Sync document IDs" (if documents without IDs)
description: "Assign IDs to all documents missing them"
- label: "Link documents to GitHub" (if orphans exist)
description: "Create/link GitHub issues for orphan documents"
# Always include these:
- label: "Continue development"
description: "Run /project:continue to work on next task"
- label: "I'm done for now"
description: "Exit status check"
```
**Based on selection:**
- "Upgrade" → Run `/blueprint:upgrade`
- "Sync" → Run `/blueprint:sync`
- "Regenerate" → Run `/blueprint:generate-rules`
- "Generate rules" → Run `/blueprint:generate-rules`
- "Update CLAUDE.md" → Run `/blueprint:claude-md`
- "Sync feature tracker" → Run `/blueprint:feature-tracker-sync`
- "Validate ADRs" → Run `/blueprint:adr-validate`
- "Sync document IDs" → Run `/blueprint:sync-ids`
- "Link documents to GitHub" → For each orphan, prompt to create/link issue
- "Continue development" → Run `/project:continue`
- "I'm done" → Exit
**Example Output**:
```
Blueprint Status
Version: v3.0.0
Initialized: 2024-01-10T09:00:00Z
Last Updated: 2024-01-15T14:30:00Z
Project Configuration:
- Name: my-awesome-project
- Type: team
- Stack: typescript, bun, react
- Rules Mode: modular
Project Documentation (docs/):
- PRDs: 3 in docs/prds/
- ADRs: 5 in docs/adrs/
- With domain tags: 4/5 (80%)
- With relationships: 2
- Status: 3 Accepted, 2 Superseded
- PRPs: 2 in docs/prps/
Work Orders (docs/blueprint/work-orders/):
- Pending: 5
- Completed: 12
- Archived: 2
Three-Layer Architecture:
Layer 1: Plugin (blueprint-plugin)
- Commands: 13 /blueprint:* commands (auto-updated)
- Skills: 3 (blueprint-development, blueprint-migration, confidence-scoring)
- Agents: 3 (requirements-documentation, architecture-decisions, prp-preparation)
Layer 2: Generated (.claude/rules/)
- Rules: 4 (3 current, 1 modified)
- ✅ architecture-patterns.md (current)
- ⚠️ testing-strategies.md (modified locally)
- ✅ implementation-guides.md (current)
- ✅ quality-standards.md (current)
Layer 3: Custom (.claude/skills/, .claude/commands/, .claude/rules/)
- Skills: 1 (my-custom-skill)
- Commands: 0
- Rules: 0 (user-maintained)
Feature Tracker:
- Status: Enabled
- Source: REQUIREMENTS.md
- Progress: 22/42 (52.4%)
- Last Sync: 2024-01-14
- Phases: 1 active, 2 complete
Traceability (ID Registry):
- Total documents: 22 (3 PRDs, 5 ADRs, 2 PRPs, 12 WOs)
- With IDs: 22/22 (100%)
- Linked to GitHub: 18/22 (82%)
- Orphan documents: 4 (PRD-002, ADR-0004, PRP-001, WO-008)
- Orphan issues: 2 (#23, #45)
- Broken links: 0
Structure:
✅ docs/blueprint/manifest.json
✅ docs/prds/
✅ docs/adrs/
✅ docs/prps/
✅ docs/blueprint/work-orders/
✅ docs/blueprint/ai_docs/
✅ docs/blueprint/feature-tracker.json
✅ .claude/rules/
✅ CLAUDE.md
Modified content detected: 1 file
Run `/blueprint:sync` to review or `/blueprint:promote testing-strategies` to preserve.
Blueprint is up to date.
```
No comments yet. Be the first to comment!