Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".
Turn a one-line objective into a step-by-step construction plan that any coding agent can execute cold.
Do not use for tasks completable in a single PR, fewer than 3 tool calls, or when the user says "just do it."
Blueprint runs a 5-phase pipeline:
plans/. Every step includes a context brief, task list, verification commands, and exit criteria — so a fresh agent can execute any step without reading prior steps.Blueprint detects git/gh availability automatically. With git + GitHub CLI, it generates full branch/PR/CI workflow plans. Without them, it switches to direct mode (edit-in-place, no branches).
/blueprint myapp "migrate database to PostgreSQL"
Produces plans/myapp-migrate-database-to-postgresql.md with steps like:
/blueprint chatbot "extract LLM providers into a plugin system"
Produces a plan with parallel steps where possible (e.g., "implement Anthropic plugin" and "implement OpenAI plugin" run in parallel after the plugin interface step is done), model tier assignments (strongest for the interface design step, default for implementation), and invariants verified after every step (e.g., "all existing tests pass", "no provider imports in core").
.md files — no hooks, no shell scripts, no executable code, no package.json, no build step. Nothing runs on install or invocation beyond Claude Code's native Markdown skill loader.This skill ships with Everything Claude Code. No separate installation is needed when ECC is installed.
If you are working from the ECC repository checkout, verify the skill is present with:
test -f skills/blueprint/SKILL.md
To update later, review the ECC diff before updating:
cd /path/to/everything-claude-code
git fetch origin main
git log --oneline HEAD..origin/main # review new commits before updating
git checkout <reviewed-full-sha> # pin to a specific reviewed commit
If you are vendoring only this skill outside the full ECC install, copy the reviewed file from the ECC repository into ~/.claude/skills/blueprint/SKILL.md. Vendored copies do not have a git remote, so update them by re-copying the file from a reviewed ECC commit rather than running git pull.
/blueprint slash command)Inspired by antbotlab/blueprint — upstream project and reference design.