craft-blueprintlisted

# Skill: Craft Blueprint > "A plan is a guess. A blueprint is a contract." ## When Use blueprint when: - Starting implementation from spec.md - Tracking multi-task feature work - Coordinating across sessions ## The Standard 1. **Source from Spec**: Tasks come from spec.md Low-Level Tasks. Never invent. 2. **Assess Ownership**: Apply `ground-delegation` criteria to assign Owner. 3. **User Confirms Completion**: Never mark `done` without user confirmation. 4. **Single In-Progress (self)**: One self task active. Multiple agent tasks allowed. 5. **Defer, Never Delete**: Out-of-scope tasks move to Deferred with reason. 6. **Log All Changes**: Every mutation recorded in Changes table. ## Ownership Each task has an Owner: `self` or `agent`. | Owner | Meaning | Status Flow | |-------|---------|-------------| | `self` | Architect does it | `pending` → `in-progress` → `done` | | `agent` | Delegated to sub-agent | `pending` → `delegated` → `in-review` → `done` | See `ground-delegation` for criteria (Bounded, Context-free, Mechanical, Verifiable). ## The Protocol 1. **Initialize**: Copy `templates/blueprint.md` to branch memory. 2. **Populate**: Extract tasks from spec.md. Assess Owner for each. 3. **Work (self)**: Mark one task `in-progress`. Sync to working.md Focus. 4. **Delegate (agent)**: Brief agent per `ground-delegation`. Mark `delegated`. 5. **Review (agent)**: When agent completes, mark `in-review`. Verify output. 6. **Complete**: User confirms. Add date to Confirmed