ProbableOdyssey | Blake Cook

The agent personas in my coding workflow

· 2 min read · 379 words

I use different agents for different jobs. The workflow starts with an idea or ticket, moves through a spec and implementation, then through two kinds of agent review. The developer makes the decisions at the gates.

TLDR:

Planner: turn ambiguity into decisions

The spec separates what is verified fact from what needs the user’s decision.

The Planner checks the ticket against the current repo, asks about missing requirements and verification, and writes a spec. If I do not agree with it, we return to the Planner. The Coder does not inherit unresolved guesses.

The goal of the spec is to provide a single artifact with all the details a coding agent needs to work in a loop without supervision (guidelines, a definition of done, and instructions on how to verify changes, surrounding context)

Coder: implement and show the evidence

Every check-in adds fatigue. So: batch decisions up front, verify continuously, report once.

The Coder works from the agreed spec in small increments, runs checks, and reports what passed and what remains unverified. It should stop for a decision it does not own, rather than quietly changing the scope.

Reviewer: make the change simpler and clearer

Report only actionable improvements worth making.

The Reviewer reads the diff and surrounding code without editing it. A useful finding identifies the location, impact, and smallest fix. The Coder can then make the change and ask the same Reviewer to check it again.

Monkey: try to break it

Find plausible correctness issues, then try to reproduce them. This is a focused adversarial investigation, not a style review or an implementation task.

The Monkey probes reachable edge cases and failure paths without changing the code. It must distinguish a reproduced failure from a plausible risk. That gives me a different signal from the Reviewer’s simplicity-focused pass.

Only then is there a draft PR. I review it before it enters the PR train; an external reviewer has another gate before merge. Feedback goes back to the Coder, not straight to production.

Reply to this post by email blZake@proZbableodyssey.blog (remove Z characters) ↪