<div align="center">

# Blueprint

**A small, principles-first workflow for AI coding.**

Clear decisions. Bounded work. Real proof. Independent review.

</div>

Blueprint gives coding agents the engineering boundaries that matter without turning software delivery into a catalogue of tiny skills. It separates repository policy, reusable phases, and end-to-end workflows so each instruction has one clear job.

## Start with the work, not the process

Use the smallest entry point that resolves the uncertainty in front of you.

| If you need to… | Start with | Result | | --- | --- | --- | | Decide what to build or resolve important technical choices | `/design` | A reviewed design with requirements and acceptance criteria | | Split a decided feature into work for several agent runs | `/plan` | Ordered tasks in chat or tracker tickets | | Take one task through delivery | `/task-to-pr` | A tested, reviewed, green pull request | | Complete every issue in a GitHub milestone | `/milestone` | One green pull request at a time, with human merge checkpoints | | Prove a change works | `/test` | Acceptance criteria mapped to evidence | | Get an independent second opinion | `/review` | Findings and a pre-merge verdict from a fresh subagent | | Simplify existing code without changing behavior | `/improve` | Clearer, smaller, better-structured code |

Small, decided work can go straight to `/task-to-pr`. Use `/design` only when decisions need review, and `/plan` only when the work needs splitting.

## How Blueprint fits together

```mermaid flowchart TB subgraph Decide["Decide only as much as needed"] Idea([Idea or problem]) --> Design["/design"] Idea -->|already decided| Task([One task]) Design -->|one task| Task Design -->|needs splitting| Plan["/plan"] --> Task end

subgraph Deliver["Deliver with /task-to-pr"] Task --> Isolate["isolate"] --> Code["code"] --> Test["/test"] --> Review["/review"] Review -->|findings| Fix["fi