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

The 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

Start free Book a demo

Phase · example runyour AI client

01Readydeveloper
02Implementdeveloper
03Verifyyou approve
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.

It is a stored workflow, not a prompt. Your AI client receives one step at a time from ConvOps over MCP, does the work, and advances. The engine holds the run at the approval until a person says yes.

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?

4 steps, in this order. Below each one is the instruction your AI receives at that step, exactly as the template stores it.

Readydeveloper

Implementdeveloper

Verifyapproval

Completeclosing note

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.
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.
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
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.

where a person decides

Where do you approve in Phase?

One step waits for a person. You answer in the chat; the engine records the verdict and the audit row records who 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 only when your AI leaves a closing note. The note is saved to the task as context, so later work can find why it ended the way it did.

what you need

What do you need to run Phase?

Read from the template's own steps: the tools they call, the files they write, and whether they touch code.

An AI client: Claude Code, Claude (desktop, web, Cowork), OpenAI Codex, ChatGPT, Cursor, OpenCode, or any MCP client. ConvOps does not run the model; your client does the work.
ConvOps: A workspace with Phase installed. It attaches to the phase task type, so new work of that type starts on it.
Tools your AI calls: workflow_advance to move between steps.
Where the work lands: Your repository: the code change and its regression test. The steps name no other files.
A repository: Yes. Steps read and change code, so run it in a coding client with your repo checked out (Claude Code, Codex, Cursor, OpenCode).
Roles named in steps: developer, reviewer. A hint for clients with subagents; one AI can run every step.

Connect your AI client first, then install Phase from the catalog in the ConvOps app. See how to connect a client

make it yours

How do you customize Phase?

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

Claude Codeexample

new chat

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 process lives in a prompt, and each run follows it a little differently

questions

Phase template FAQ

Where does a phase read its specification?

From its parent plan. The Ready step reads the phase file under the plan's docs directory (scope, approach, verification) and raises anything unclear or any unmet dependency before implementation starts.

What happens when the phase completes?

The parent plan's Execute Phases step sees it. That step waits until every child phase is completed or cancelled before the plan moves on to its own verification.

Can I use the Phase template without the Plan template?

It attaches to the phase task type, so it runs for any phase task. Its Ready step expects a spec from a parent plan, so it is designed to run under the Plan template.

Which AI clients can run the Phase template?

Any MCP client connected to ConvOps. Verified clients: Claude Code, Claude (desktop, web, Cowork), OpenAI Codex, ChatGPT, Cursor, OpenCode. Because its steps change code, run it in a coding client with your repository checked out.

Workflows that run next to it

engineering

FeatureDeliver features from requirements to reviewed release. The AI drives through Capture, planning, execution, and Verify.7 steps · 4 gates

universal

PlanTurn strategic work into reviewed, executable plans. The AI drives through Analyze, Draft, phases, and execution.10 steps · 5 gates

universal

TaskTake any work item from intake to verified completion. The AI drives through Intake, Analyze, Implement, and Verify.6 steps · 3 gates

universal

GoalDrive strategic objectives from definition to completion. The AI drives through Capture, Active tracking, and Review.4 steps · 4 gates

your next step

Teach it once. Then let it run.

on your ownStart freeConnect your AI tool in one line. Nothing to install.with your teamBook a demoWe show ConvOps on your team's real work.keep readingThe Project Planning kitPhase with the workflows it connects to.