Editorial recipe — used internally

Ship a focused software change

For teams with a repository and executable acceptance checks.

Stack

Claude Code or Codex → Ponytail → Project checks → Different model reviewer

Run this recipe

Work through it here

Progress stays in this browser. The downloaded Markdown kit works in any notes app or repository.

0/5 complete

State one outcome, repository scope, constraints, and the proof required.
Let the coding harness inspect existing patterns before editing; add Ponytail when bloat is the likely failure.
Run the smallest test that catches the changed behavior, then the real lint and build gates.
Have a different model review the diff and logs against the original acceptance criteria.
Ship only after a fresh runtime proves the user-visible path.

State one outcome, repository scope, constraints, and the proof required.
Let the coding harness inspect existing patterns before editing; add Ponytail when bloat is the likely failure.
Run the smallest test that catches the changed behavior, then the real lint and build gates.
Have a different model review the diff and logs against the original acceptance criteria.
Ship only after a fresh runtime proves the user-visible path.

A reviewed diff with test, build, and runtime evidence

Do not grant write or deploy permission to an agent that only needs review access.