blueprint

name	blueprint
description	Transform a design into an implementation spec. Creates a blueprint document and an implementation prompt for /plan mode. Use after /design or /research.
disable-model-invocation	false
argument-hint	[design-ref or topic]
allowed-tools	Read, Grep, Glob, Write
wrought	{"version":"1.0","tools":{"capabilities":["read_file","search_content","find_files","write_file"]},"platforms":{"claude-code":{"allowed-tools":"Read, Grep, Glob, Write","disable-model-invocation":false}},"agent":{"role":"Implementation Architect","expertise":["implementation planning","dependency analysis","risk assessment"],"non_goals":["writing production code","running tests"]},"execution":{"default_mode":"self-refine","max_iterations":8,"max_refine":1,"stop_conditions":["Blueprint written to docs/blueprints/","Implementation prompt written to docs/prompts/","User instructed to stop"]},"output":{"format":"markdown","template":"docs/blueprints/{YYYY-MM-DD_HHMM}_{feature_name}.md","required_sections":["Objective","Requirements","Architecture Decisions","Scope","Files Affected","Implementation Sequence","Acceptance Criteria"],"prohibited_content":["credentials","secrets"]},"pipeline":{"track":"proactive","standalone":false,"prerequisites":["docs/design/*.md","docs/research/*.md"],"produces":["docs/blueprints/*.md","docs/prompts/*.md"],"suggested_next":["plan"]}}

Blueprint Procedure

Trigger: Use /blueprint {feature description} when transforming design and research output into an implementation specification and prompt for /plan mode.

Examples:

• /blueprint CSV migration with schema drift detection
• /blueprint add real-time WebSocket notifications to the monitoring dashboard
• /blueprint migrate authentication from session-based to JWT

Prerequisites

Before executing this skill, verify ALL of the following:

1. Use Glob to check for: docs/design/*.md
   • If NO match -> STOP: "Run /design first to create a design document."
   • If user says --force, proceed without validation.
2. Read the most recent Findings Tracker matching *_FINDINGS_TRACKER.md
   • Identify the relevant finding (ask user if ambiguous)

Pre-flight Check

1. Verify artifact prerequisites (above)
2. Identify which finding/workflow this is for
3. Load finding report and related artifacts for context
4. Proceed to main skill instructions

---

Instructions

The user has described a feature or change to implement. Reason thoroughly about how to turn existing design and research artifacts into a concrete implementation specification.

Feature to blueprint: The argument passed after /blueprint

---

CRITICAL: File Naming Convention

ALL files MUST use this exact format: {YYYY-MM-DD_HHMM}_{feature_name}.md

✅ 2026-01-27_1200_csv_migration_schema_drift.md ❌ BLUEPRINT_CSV_MIGRATION_2026-01-27.md — no prefix, date comes FIRST

---

Context Check

See context_check.md

• Task type: "Blueprint" / Output: docs/blueprints/

---

Findings Tracker Update Protocol

See tracker_update_checklist.md