Plan AI workflow template: A plan you review before anything runs.

The ConvOps Plan template makes your AI write an implementation plan as files, put it in front of you through an embedded review fragment, create one child task per phase, and hold until every phase is finished. Three approvals sit on the path: the review, the go-ahead and the final verify.

10 steps · 3 approvals · 2 loops back · waits for child tasks

Plan · example runyour AI client
  1. 01Analyzeplanner
  2. 02Draftplanner
  3. fragment · review-and-approve03Prepare Reviewreviewer
  4. 04Apply Fixesdeveloper
  5. 05Reviewwaits for approval
  6. 06Create Phasesplanner
  7. 07Ready to Executewaits for approval
  8. 08Execute Phaseswaits on children
  9. 09Verifywaits for approval
  10. 10Completeclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the Plan template do?

For teams who want an AI to plan migrations, roadmaps and refactors as reviewable documents before any phase starts.

Plan is stored in ConvOps as 10 steps, and your AI client receives them one at a time. A Plan run holds at Review and Ready to Execute and Verify until an explicit approval is given.

  • Plan a Q2 roadmap from analysis to executed, verified phases
  • Break a database migration into reviewable phases before any run
  • Design an API-versioning strategy with sign-off before execution
step by step

How does the Plan workflow run?

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

Analyzeplanner
Draftplanner
Prepare Reviewreviewer
Apply Fixesdeveloper
Reviewapproval
Create Phasesplanner
Ready to Executeapproval
Execute Phaseswaits on children
Verifyapproval
Completeclosing note

A folder of plan files (an analysis, an overview and one file per phase) that you review, followed by one child task per phase.

  1. 01

    Analyze

    the agent worksrole · planner

    Analyze the plan's scope and approach. Read the parent initiative for goal alignment and constraints.

    Produce docs/plans/{task-slug}/analysis.md with:

    • Surface area: components, files, or systems this plan touches
    • Approach: 3–5 sentences describing HOW
    • Dependencies: other plans, external systems, integration points
    • Risks and unknowns

    Keep each section tight. The draft step expands the plan; analysis captures the shape.

  2. 02

    Draft

    the agent worksrole · planner

    Draft the plan as files under docs/plans/{task-slug}/.

    Create:

    • overview.md: title, one-paragraph outcome, enumerated phase list (title + one-line summary each), sequencing notes if order matters, and a plain-English acceptance statement for the plan as a whole
    • One file per phase under phases/, named phase-NN-short-slug.md (NN is a zero-padded index, slug is a short kebab-case phase name). Each file contains: Scope (what this phase delivers and what it excludes), Approach (the work to do), Verification (how to confirm this phase is done)

    Prefer fewer, broader phases over many narrow ones. Do NOT create phase tasks yet: that is the next step.

  3. embedded fragment · review-and-approve · a reusable block the engine runs in place

    03

    Prepare Review

    the agent worksrole · reviewer

    Summarize the decision the operator needs to make in one paragraph. Include:

    • What changed
    • Why it changed
    • What could go wrong if approved as-is

    Keep it under 10 lines. Do not restate the whole task.

  4. 04

    Apply Fixes

    the agent worksrole · developer

    Apply the changes the operator requested, then advance with workflow_advance (no approved verdict). Do not make changes the operator did not ask for.

  5. 05

    Review

    waits for your approval

    Present the prepared decision to the operator. Approve with workflow_advance(approved=true) to continue; reject with workflow_advance(approved=false) to send it for fixes. Never record a verdict the operator did not give.

    rejected → back to Apply Fixes

  6. 06

    Create Phases

    the agent worksrole · planner

    Create one child task per phase defined in docs/plans/{task-slug}/phases/. For each phase file:

    • type: phase
    • title and summary: from the phase file
    • status: backlog (the phase's own workflow takes over from there)

    Attach every phase task to this plan as the parent. Confirm all phase tasks were created and linked before advancing.

  7. 07

    Ready to Execute

    waits for your approval

    Plan and phase tasks exist. Request operator go-ahead before advancing to execute-phases: this lets the parent initiative pipeline sequence plans.

    no rejection path · the run moves on only when approved

  8. 08

    Execute Phases

    waits for child tasks

    Phase execution is in progress. This step blocks until every child phase reaches a terminal state (completed or cancelled). Address stalls on the phase's own workflow: not here.

  9. 09

    Verify

    waits for your approvalrole · reviewer

    Validate the plan's integration. Each phase was verified in isolation; confirm they combine into the plan's promised outcome. Report scenario exercised, what worked, what didn't, and which phase owns any gap. Reject to reopen execute-phases. Request operator approval before advancing.

    rejected → back to Execute Phases

  10. 10

    Complete

    closes with a note

    Plan shipped. Mark it complete.

reach for it when

  • The work needs a written plan that someone signs off before it starts.
  • It breaks into phases that must land in a known order.
  • Risks and verification should be written down per phase, not discovered halfway.

something else fits when

  • The scope is a single change you could describe in a paragraph.
  • Nobody will read the plan before execution, so the review adds nothing.
  • You are still deciding whether to do the work at all: write a Decision Memo first.
example · finance systemsenterprise

Moving the general ledger to a new ERP

The agent writes the analysis and four phase files: chart of accounts, historical balances, parallel run and cut-over. The finance director approves the review, the phase tasks appear, and nothing runs until the go-ahead.

Review fragment and Ready to Execute approval

where approval is required

Where do you approve in Plan?

Plan holds at Review and Ready to Execute and Verify until an explicit approval is given, recorded with the account that gave it.

step 5

Review

Your AI has summarized what changed, why, and what could go wrong. Approve to continue, or reject to send the plan to Apply Fixes and back to you.

reject → back to Apply Fixes

step 7

Ready to Execute

Phase tasks exist but nothing runs yet. Your go-ahead lets a parent initiative sequence its plans.

no rejection path · approve to continue

step 9

Verify

Every phase was verified alone. Here you confirm they combine into the outcome the plan promised. Reject it and the run returns to Execute Phases.

reject → back to Execute Phases

gates the engine checks without you

  • Execute Phases waits until every child task Plan created is completed or cancelled.
  • Complete closes Plan only when your AI leaves a closing note, saved on the task.
what you need

What do you need to run Plan?

make it yours

How do you customize Plan?

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

Claude Codeexample

new chat

In Draft, add a Risks section to overview.md with a mitigation for each risk.
workflow_step_update · Plan
Done. Plan in your workspace now has the change, and every new run follows it.

more example prompts

  • "In Draft, add a Risks section to overview.md with a mitigation for each risk."
  • "Remove the Ready to Execute approval: start phases as soon as they are created."
  • "Store plans under planning/{task-slug}/ instead of docs/plans/."
the difference

Plan: without a workflow vs with it

  • A vague plan gets handed off and the team builds before the approach is agreed
  • There is no record of which approach was chosen or why it changed mid-flight
  • The plan is marked done while half its phases are still open
  • The Plan process lives in a prompt, and each run follows it a little differently
  • The AI drives through Analyze and Draft, then pauses at an approval step so you sign off before phases are created
  • Every step (Analyze, Draft, phase creation, execution, Verify) is logged automatically, so the audit trail is already there
  • The AI cannot close the plan until every child phase completes, so done means done
  • Your AI receives the 10 stored steps one at a time, and the run holds at Review and Ready to Execute and Verify until an explicit approval is given
questions

Plan template FAQ

What is the ConvOps Plan template?

The ConvOps Plan template makes your AI write an implementation plan as files, put it in front of you through an embedded review fragment, create one child task per phase, and hold until every phase is finished. Three approvals sit on the path: the review, the go-ahead and the final verify.

What files does the Plan template create?

In ConvOps, Analyze writes docs/plans/{task-slug}/analysis.md with the surface area, the approach, dependencies, and risks and unknowns. Draft writes overview.md in the same folder, with the outcome, the phase list and an acceptance statement, plus one phase-NN-short-slug.md file per phase under phases/, each with its scope, approach and verification.

What is the review-and-approve fragment?

A reusable ConvOps block of three steps embedded in the plan. Prepare Review summarizes in under 10 lines what changed, why, and what could go wrong. Review puts that decision to you, and your AI is told to record only the verdict you gave. A rejection goes to Apply Fixes, which applies only the changes you requested and returns to the review.

How do phases run?

In ConvOps, Create Phases makes one child task per phase file, each attached to the plan and starting in backlog on its own Phase workflow. The Ready to Execute approval then holds the run until you give the go-ahead, and Execute Phases waits until every child phase is completed or cancelled before the plan moves on to its own Verify.

What does the final Verify check?

Each phase was verified alone, so the ConvOps Plan Verify step checks the integration: whether the phases combine into the outcome the plan promised. The reviewer reports the scenario exercised, what worked, what did not, and which phase owns any gap. Rejecting it returns the run to Execute Phases, and Complete follows only after Verify is approved.