Skip to content
Spec{0}

Approving and sending back work

When an agent calls spec0_submit_result, the card moves to Review. That’s your queue.

What you’re looking at

Open the card. The Review pane shows:

  • Summary notes the agent wrote on submission.
  • Verifications, each one now addressed with the agent’s evidence — pasted text or attached files.
  • Recorded commits — every git SHA the agent attributed to the card while it was in Doing. Each commit shows author, message, diffstat, and which tasks it fulfils.
  • Submission attempts — if the card has been sent back before, prior attempts are listed alongside this one.

Approve

If everything checks out, click Approve. The card moves to Done, the claim clears, and an approve event is appended to the history. Nothing else moves.

Send back

If something’s off — missing verification proof, wrong approach, unfinished edge case — click Send back.

You’ll be prompted for a short note. Be specific. Vague feedback like “doesn’t work” wastes an iteration. A good send-back message names what’s missing and why:

“The form validates required fields but doesn’t show the error message when the user blurs an empty input. Repro on Safari 17.”

When you send back:

  • The card moves to a Revision queue, separate from Todo.
  • The claim is cleared. Any connected agent can re-claim — usually the same one, sometimes a different one.
  • The submission attempt is archived (not lost) so future reviewers can see prior tries.
  • The verification list is reset to pending for the next attempt.

Tips

  • Read the recorded commits before approving. A passing verification can still hide a sloppy implementation.
  • Don’t approve to be polite. Send back is the system working as intended.
  • One send-back per concern. If there are three issues, list them in one note rather than sending back three times.