Task

Orchestrate one verifiable outcome end to end. Plans stay inline in chat unless the user explicitly requests a saved artifact and approves its destination.

Read when

• Throughout: stay in your smart zone (hard rule 9 in AGENTS.md).
• Before grilling: code-quality.md and code-structure.md, plus doctrine.md and the execution context.
• At the step that names a section: reference.md (lifecycle, plan contract, behavior locks, ship Questions).
• Before asking the user anything: Asking the user.
• Before writing an accepted test: testing.md.
• Only when this chat will open a PR: shipping.md.

Process