From blueprint-mode
Show overview of project's Blueprint structure including specs, ADRs, and patterns. Use when the user asks about documented decisions, project status, or wants to see what's been captured.
npx claudepluginhub rickardp/blueprint-mode --plugin blueprint-modeThis skill is limited to using the following tools:
Display an overview of the project's spec-driven development structure.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Display an overview of the project's spec-driven development structure.
Invoked by: /blueprint:status or when user asks "what's documented?", "show me the specs", or "blueprint status".
docs/adrs/*.md, no index needed.Tool Preferences:
find or ls)cat)Look for these directories:
docs/specs/docs/adrs/patterns/If none exist:
No Blueprint structure found.
Run `/blueprint:setup-repo` for a new project, or `/blueprint:onboard` for an existing codebase.
Use parallel operations to minimize latency. Gather all information in a single batch:
Run these checks in parallel (single glob + batch file reads):
# Single glob to find all relevant files
# Pattern: docs/specs/*.md, docs/adrs/*.md, patterns/good/*, patterns/bad/*.md, CLAUDE.md
Glob patterns to check:
docs/specs/{product,tech-stack,boundaries}.md - Core spec filesdocs/specs/features/*.md - Feature specs (discovered via globbing)docs/specs/non-functional/*.md - NFR files (discovered via globbing)docs/adrs/*.md - All ADR files (discovered via globbing)patterns/good/* - Good pattern files (excluding .gitkeep)patterns/bad/anti-patterns.md - Anti-patterns fileCLAUDE.md - Agent instructionsIn one batch read:
docs/adrs/*.md file - parse frontmatter for status (Active/Superseded/Deprecated/Draft)patterns/bad/anti-patterns.md - count ## headingsCLAUDE.md - check for "Pre-Edit Checklist" section| Category | Check | Source |
|---|---|---|
| Specs | product.md exists | glob |
| Specs | tech-stack.md exists | glob |
| Specs | boundaries.md exists | glob |
| Specs | Feature spec count | glob docs/specs/features/*.md |
| Specs | NFR file count | glob docs/specs/non-functional/*.md |
| ADRs | Active count | ADR files with status: Active |
| ADRs | Superseded count | ADR files with status: Superseded |
| ADRs | Deprecated count | ADR files with status: Deprecated |
| ADRs | Draft count | ADR files with status: Draft |
| ADRs | Most recent | highest number in Active ADRs |
| Patterns | Good count | glob (exclude .gitkeep) |
| Patterns | Bad count | ## headings in anti-patterns.md |
| CLAUDE.md | Exists + has checklist | file check + "Pre-Edit Checklist" search |
## Blueprint Status for [Project Name]
### Specs
- Product: docs/specs/product.md [exists ? "✓" : "✗ missing"]
- Tech Stack: docs/specs/tech-stack.md [exists ? "✓" : "✗ missing"]
- Boundaries: docs/specs/boundaries.md [exists ? "✓" : "✗ missing"]
- Features: [count] feature specs
- Non-Functional: [count] NFR files
### ADRs
- Active: [count]
- Draft: [count] (needs refinement)
- Superseded: [count] (consider deleting if no code references)
- Deprecated: [count] (consider deleting if no code references)
- Recent: ADR-[NNN] "[title]" ([date])
### Patterns
- Good: [count] examples in patterns/good/
- Bad: [count] anti-patterns documented
### CLAUDE.md
[exists && hasChecklist ? "✓ Pre-Edit Checklist present" : "✗ Missing or incomplete"]
Note: ADRs are discovered via globbing docs/adrs/*.md and reading their frontmatter status field.
If only partial structure exists:
## Blueprint Status
### Found
- docs/adrs/ (2 ADRs)
### Missing
- docs/specs/ - Run `/blueprint:onboard` to create
- patterns/ - Run `/blueprint:good-pattern` to add examples
- CLAUDE.md Documentation section
Run `/blueprint:onboard` to complete the setup.
Offer helpful next actions based on what's missing or incomplete:
Onboarding:
/blueprint:onboard to continue. Pending: [list pending sections]"/blueprint:onboard to set up incremental tracking"ADRs:
/blueprint:decide to record your first decision"/blueprint:decide [topic] to complete them"Patterns:
/blueprint:good-pattern to capture approved code"Structure:
docs/specs/boundaries.md with /blueprint:onboard"/blueprint:status → Full overview