Phase AI workflow template: One phase, from ready to verified.

The ConvOps Phase template makes your AI execute one chunk of a larger plan: confirm the phase spec is clear and its dependencies are met, implement inside that scope, then run the phase's own verification. You approve the result. A failure loops back to Implement and verification reruns from scratch.

4 steps · 1 approval · 1 loop back

Phase · example runyour AI client
  1. 01Readydeveloper
  2. 02Implementdeveloper
  3. 03Verifywaits for approval
  4. 04Completeclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the Phase template do?

For teams running multi-phase plans, where each phase is one task an AI developer can pick up cold.

Phase is stored in ConvOps as four steps, and your AI client receives them one at a time. A Phase run holds at Verify until an explicit approval is given.

  • 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
step by step

How does the Phase workflow run?

The 4 Phase steps in order, each with the instruction your AI receives there as Phase stores it.

Readydeveloper
Implementdeveloper
Verifyapproval
Completeclosing note

One phase of a plan implemented inside its stated scope, with the phase's own verification run and its result kept on the task.

  1. 01

    Ready

    the agent worksrole · 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. 02

    Implement

    the agent worksrole · 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. 03

    Verify

    waits for your approvalrole · 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.

    rejected → back to Implement

  4. 04

    Complete

    closes with a note

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

reach for it when

  • A parent plan already wrote this phase's scope, approach and verification.
  • A different agent or person should be able to pick the phase up cold.
  • A failed check should send the work back instead of being patched on the spot.

something else fits when

  • There is no parent plan, so the Ready step has no spec to read.
  • The work stands alone, which is what Task is for.
  • The phase is still vague: fix its plan file first.
example · data platform

Phase 2 of a warehouse migration

Ready confirms phase 1 landed and that the spec lists the tables to move. The agent moves them, Verify runs the row-count checks the spec names, and one mismatch sends the run back to Implement.

Verify approval with a loop to Implement

where approval is required

Where do you approve in Phase?

Phase holds at Verify until an explicit approval is given, recorded with the account that gave it.

step 3

Verify

The reviewer runs the verification written in the phase spec and reports what passed and what failed. Reject it and the run returns to Implement. Issues are never patched inline.

reject → back to Implement

gates the engine checks without you

  • Complete closes Phase only when your AI leaves a closing note, saved on the task.
what you need

What do you need to run Phase?

make it yours

How do you customize Phase?

Once installed, Phase is a workflow in your workspace. Ask your AI to change Phase in plain words; the edit lands on the one step that needs it.

Claude Codeexample

new chat

In Ready, also require the phase spec to list the files it expects to change.
workflow_step_update · Phase
Done. Phase in your workspace now has the change, and every new run follows it.

more example prompts

  • "In Ready, also require the phase spec to list the files it expects to change."
  • "Add a step after Implement that updates the plan overview with what this phase delivered."
  • "Make Verify also run the linter before asking me."
the difference

Phase: without a workflow vs with it

  • A phase is called done the moment the code compiles, with no real check
  • There is no trace of what was built in this phase or whether it was verified
  • Each phase is executed differently depending on who picks it up
  • The Phase process lives in a prompt, and each run follows it a little differently
  • The AI drives through Implement, then pauses at an approval step before the phase is marked complete
  • Every step (Ready, Implement, Verify) is logged automatically, so the audit trail is already there
  • The AI drives the same four-step phase process every time, with verification before completion
  • Your AI receives the 4 stored steps one at a time, and the run holds at Verify until an explicit approval is given
questions

Phase template FAQ

What is the ConvOps Phase template?

The ConvOps Phase template makes your AI execute one chunk of a larger plan: confirm the phase spec is clear and its dependencies are met, implement inside that scope, then run the phase's own verification. You approve the result. A failure loops back to Implement and verification reruns from scratch.

Where does a phase read its specification?

From its parent plan. The ConvOps Ready step reads the phase file under the plan's docs directory, with its scope, approach and verification, and confirms the scope is clear, the approach is actionable, verification criteria exist and dependencies from earlier phases are met. Anything unclear or unmet is raised at Ready, before implementation starts.

What happens when the phase completes?

The parent plan's Execute Phases step in ConvOps sees it. That step waits until every child phase is completed or cancelled, then the plan moves on to its own Verify, which checks that the phases combine into the promised outcome. A phase reaches Complete only after its own Verify is approved, so a finished phase is a verified one.

Can I use the Phase template without the Plan template?

Not on its own. In ConvOps a phase task always lives under a plan: it is the one structural rule in the task hierarchy. The Phase template attaches to the phase task type, and its Ready step reads the specification from that parent plan, so it is designed to run under the Plan template, which creates one phase task per phase file.

What happens when phase verification fails?

In ConvOps, the reviewer at Verify runs the verification written in the phase specification and reports what was checked, what passed and what failed. If anything fails, the step is rejected and the run loops back to Implement. Issues are not patched inline: the developer fixes them, then verification re-runs from scratch before the run holds for approval again.