blueprint

Topics in the source

• Blueprint — Construction Plan Generator
• When to Use
• How It Works
• Examples
• Basic usage
• Multi-agent project
• Key Features
• Installation

Turn a one-line objective into a step-by-step construction plan that any coding agent can execute cold. Breaking a large feature into multiple PRs with clear dependency order Planning a refactor or migration that spans multiple sessions Coordinating parallel workstreams across sub-agents Any task where context loss between sessions would cause rework 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: 1. Research — Pre-flight checks (git, gh auth, remote, default branch), then reads project structure, existing plans, and memory files to gather context. 2. Design — Breaks the objective into one-PR-sized steps (3–12 typical). Assigns dependency edges, parallel/serial ordering, model tier (strongest vs default), and rollback strategy per step. 3. Draft — Writes a self-contained Markdown plan file to 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. 4. Review — Delegates adversarial review to a strongest-model sub-agent (e.g., Opus) against a checklist and anti-pattern catalog. Fi

This is an excerpt. Refer to the complete source and its current requirements.