template

Phase

Execute an implementation phase from ready to verified. The AI drives through Ready, Implement, and Verify.

the steps, as stored

  1. 01Readyagent: developer

    Read this phase's specification from the parent plan — typically a file under the plan's docs directory describing scope, approach, and verification for this phase.

    Confirm: - Scope is clear (what to deliver and what to exclude) - Approach is actionable (you know what to build) - Verification criteria exist (you know how to prove it works) - Any dependencies from earlier phases are met

    If anything is unclear or a dependency is unmet, raise it now before starting implementation.

  2. 02Implementagent: developer

    Execute the work described in the phase specification. Keep changes focused on this phase's scope — do not scope-creep into adjacent work.

    Run tests after each significant change to catch regressions early.

  3. 03Verifyapproval gateagent: reviewer

    Run the verification defined in the phase specification. Report what you checked, what passed, and what failed.

    If anything fails, reject to loop back to implement. Do not patch issues inline — the developer fixes, then verification re-runs from scratch.

    Request operator approval before advancing.

  4. 04Completecontext gate

    Phase complete. The parent plan's execute-phases step will detect this and advance to the next phase automatically.

use it for

  • Implement phase 3 of an auth refactor with verification before close
  • Execute a migration-testing phase from ready state to verified
  • Run one chunk of a larger plan end to end with quality gates

without it, with it

without with phase
A phase is called done the moment the code compiles, with no real checkThe AI drives through Implement, then pauses at an approval step before the phase is marked complete
There is no trace of what was built in this phase or whether it was verifiedEvery step — Ready, Implement, Verify — is logged automatically, so the audit trail is already there
Each phase is executed differently depending on who picks it upThe AI drives the same four-step phase process every time, with verification before completion

say this in your client

"Implement phase 3 of the auth refactor""Execute the migration testing phase"