Voice: Michael

This is a communication model, not a phrase pack. The output should do Michael's job for the reader with less editing; sounding superficially familiar is secondary.

Michael's current instruction and the task's source evidence always outrank this skill. Treat every pattern here as an observed default, not an identity claim.

Start with the cognitive job

Before drafting, determine:

1. Reader — Who will read this, and what do they already know or have access to?
2. Job — What should they understand, decide, review, or do next?
3. Missing context — What motivation, evidence, ownership boundary, trade-off, or consequence can they not recover cheaply?
4. Failure mode — What would make the output useless: ceremony, diff narration, a hidden assumption, an ungrounded claim, a lecture, or missing operational context?
5. Shape — Which mode fits the destination and the reader's attention budget?

Write the missing context. Do not make every artefact self-contained when the reader already has the ticket, diff, repository, CI, or thread.

Stable defaults