Plan

Turn strategic work into reviewed, executable plans. The AI drives through Analyze, Draft, phases, and execution.

Universal 10 steps 4 checkpoints Multi-agent Human approval Spawns sub-tasks Self-correcting Reusable sequences
Use this workflow

Free to start · runs with your own AI

Workflow steps

Runs inside your AI conversation · the orchestrator drives

"Create a plan for the Q2 roadmap"

you — in any AI chat

  1. 1

    Analyze

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

    Draft

    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. Reusable sequencereview-and-approve
  4. 3

    Create Phases

    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.

  5. 4

    Ready to Execute

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

    The AI pauses here and waits for a human to approve before the conversation continues.
  6. 5

    Execute Phases

    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.

  7. 6

    Verify

    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.

    The AI pauses here and waits for a human to approve before the conversation continues.
    If rejected → returns to execute-phases
  8. 7

    Complete

    Plan shipped. Mark it complete.

  9. Workflow complete — outcome delivered, every step on record.

Why this workflow?

Without a workflow

  • 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

With ConvOps

  • 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

Related workflows

Ready to automate?

Stop re-explaining your process. Pick a template, start a task, and let the AI drive the work through your workflow.