Menu
Capture decisions and context from the current conversation into blueprint docs, DESIGN.md, and design trees
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | blueprint:capture |
| description | Capture decisions and context from the current conversation into blueprint docs, DESIGN.md, and design trees |
| argument-hint | [optional: specific topic to capture] |
| allowed-tools | ["Glob","Grep","Read","Write","Edit","AskUserQuestion"] |
COMMAND: Extract decisions, rationale, and context from the current conversation and persist them into the appropriate blueprint documents — across the code/architecture tree, DESIGN.md, and the design/UX tree.
Detect design availability — Glob for DESIGN.md and design/ux-decisions/. DESIGN.md may exist without the opt-in design tree. If design/ux-decisions/ doesn't exist, UX decisions are skipped — never silently filed as ADRs — but cross-cutting design rules can still update DESIGN.md when it exists.
Scan the current conversation for:
design/ exists): interaction model, navigation, modal vs page, empty/error states, motionDESIGN.md exists): visual rules, token usage, type scale, voice/tone, broad prohibitionsIf argument provided: Focus capture on that specific topic only.
If design content was discussed but the right design artifact doesn't exist: Note this in the preview. Don't misfile it.
design/ tree: suggest /blueprint:onboard-designDESIGN.md: suggest /blueprint:onboard-design to scaffold it, or create DESIGN.md only if the user explicitly confirms in this capture flowRead existing docs to avoid duplicates:
docs/adrs/*.md — existing architectural decisionsdocs/specs/features/*.md — existing feature specspatterns/good/ and patterns/bad/anti-patterns.md — existing patternsDESIGN.md — cross-cutting design rules (if present)design/ux-decisions/*.md — existing UX decisions (if tree exists)Classify each captured item — respect tree separation, never file design content under docs/ or code content under design/. Design destinations are only valid when design/ exists:
| Type | Destination | Action |
|---|---|---|
| New architectural decision | docs/adrs/NNN-slug.md | Create Draft ADR |
| Refinement of existing ADR | Existing ADR | Update (add context, resolve TODOs, promote Draft→Active) |
| New UX decision | design/ux-decisions/NNN-slug.md | Create Draft UX decision |
| Refinement of existing UX decision | Existing UX decision | Update |
| Cross-cutting design rule | DESIGN.md | Append or update the relevant short section |
| New feature/requirement | docs/specs/features/slug.md | Create with maturity: Exploring |
| Refinement of existing feature | Existing feature spec | Update requirements, implementation state, maturity |
| Implementation progress | Existing feature spec | Update Implementation State section |
| Good pattern agreed on (any subject) | patterns/good/name.ext | Create pattern file |
| Anti-pattern identified (any subject) | patterns/bad/anti-patterns.md | Append section |
| Open question resolved | Existing spec / ADR / UX decision | Remove TODO, fill in answer |
Preview — Show the user what will be captured before writing. If design content was scanned but skipped due to missing tree, list those skipped items separately. Only show the "Skipped" block when at least one design item was actually scanned and skipped — if the conversation had no UX/design content, omit it entirely (don't narrate design-tree absence as a reason for not capturing things that were never there):
Found N items to capture:
1. [UPDATE] docs/specs/features/foo.md — Add implementation state, advance maturity to Building
2. [CREATE] docs/adrs/005-caching-strategy.md — Draft ADR for Redis caching decision
Skipped (design tree not set up — run /blueprint:onboard-design to capture these):
- 1 UX decision (modal vs full page for confirmations)
- 1 DESIGN.md rule (imperative CTA voice) — DESIGN.md not present
Confirm — Ask: "Proceed with all, or select specific items?"
Write confirmed items using templates from _templates/TEMPLATES.md
Report what was captured and where (and what was skipped)
Captured from conversation:
- Created docs/adrs/005-caching-strategy.md (Draft)
- Updated docs/specs/features/notifications.md:
- Maturity: Exploring → Building
- Added 2 requirements
- Updated implementation state: "Database schema designed"
- Updated docs/adrs/003-shell-hooks.md: resolved 1 TODO
Context is now persisted. Safe to start a new session.
Record a decision or cross-cutting design rule with rationale. Triages tech vs UX vs DESIGN.md rules vs requirements into the right document type and tree.
Explain Blueprint Mode plugin and available commands. Use when the user asks about Blueprint features, how to use skills, or needs guidance on the intent-capture workflow.
Opt-in. Add design intent capture to a Blueprint repo. Scaffolds design/ux-decisions/, offers to scaffold a minimal community-format DESIGN.md if absent, and can optionally surface a small number of candidate UX decisions found in existing UI/code for the user, developer, or designer to confirm.
Create Blueprint structure from existing repo. Run multiple times to refine.
Show overview of project's Blueprint structure plus important adjacent DESIGN.md context. Use when the user asks about documented decisions, project status, or wants to see what's been captured.
Set up a new repository with Blueprint intent-capture structure from scratch. Use when creating a new project and the user wants to establish specs, ADRs, and patterns from the beginning.