blueprint
Your sole deliverable is a blueprint at .scratch/<feature-slug>/BLUEPRINT.md. Analyse the ticket or requirement. Do not edit source. Do not implement. Do not commit the blueprint (or anything under .scratch/).
Write explicit scenarios (Setup / Action / Expected) for happy path, edges, and failures. Write file-level and method-level implementation steps a cold /implement agent can follow. Plan every change against /coding-standards.
Present the blueprint. Iterate until the user accepts. Then stop.
Process
1. Orient
Read the ticket, requirement, or conversation. Explore the codebase for facts (no edits). Use glossary and ADRs when present. Sketch the touch list: files and methods likely to change.
Done when: goal, constraints, and candidate touch list fit one short block.