Project Planning AI workflow kit: Plan it, phase it, ship it.

The ConvOps Project Planning kit gives your AI four connected workflows for delivery without strategic goals: Feature breaks an initiative into plans, Plan writes phases, Phase executes one chunk, and Task handles everything small. Parents wait for their children, and you approve the breakdown, the plan and every verification.

4 templates · 27 steps · 8 approvals · 5 loops back

kit · 4 workflowsreal steps
  1. 01Feature7 steps · 2 approvals
  2. 02Plan10 steps · 3 approvals
  3. 03Phase4 steps · 1 approval
  4. 04Task6 steps · 2 approvals

one chip per stored step · square chips wait for an explicit approval

the set

What's in the Project Planning kit?

Four Project Planning templates, installed together, each received by your AI one step at a time.

Four linked workflows that take an initiative from breakdown to verified phases, with Task for anything too small to plan.

01 · 7 steps · 2 approvals

Feature

The top of a Project Planning run: it turns one request into approved child plans and tasks, then verifies they add up.

  1. Capture
  2. Define Plans
  3. Create Plans
  4. Execute Plans
  5. Verify
  6. Capture Learnings
  7. Complete
  • Ship a dark-mode toggle from spec to verified release
  • Add CSV export end to end: capture, build phases, review, verify
every step of Feature →

02 · 10 steps · 3 approvals

Plan

In Project Planning, Plan writes the analysis and phase files for one approved item and waits for its phases.

  1. Analyze
  2. Draft
  3. Prepare Review
  4. Apply Fixes
  5. Review
  6. Create Phases
  7. Ready to Execute
  8. Execute Phases
  9. Verify
  10. Complete
  • Plan a Q2 roadmap from analysis to executed, verified phases
  • Break a database migration into reviewable phases before any run
every step of Plan →

03 · 4 steps · 1 approval

Phase

One chunk of a Project Planning plan, built inside its own scope and verified on its own criteria.

  1. Ready
  2. Implement
  3. Verify
  4. Complete
  • Implement phase 3 of an auth refactor with verification before close
  • Execute a migration-testing phase from ready state to verified
every step of Phase →

04 · 6 steps · 2 approvals

Task

The Project Planning route for work too small to plan: a one-screen plan, the change and a check.

  1. Intake
  2. Analyze
  3. Implement
  4. Verify
  5. Capture Learnings
  6. Complete
  • Refactor an authentication module with review before it ships
  • Update API documentation from request to verified change
every step of Task →

reach for it when

  • For delivery leads who run projects from a request, with no quarterly goal above them.
  • Your work mixes multi-phase projects with a steady stream of small tasks.
  • Every parent should wait for its children before it closes.

something else fits when

  • Kit vs kit: when the work rolls up to a measurable goal, Strategic Delivery adds the Goal level and leaves Task out.
  • Your team only does small, one-step work, so Task alone is enough.
  • Your work is content or sales rather than delivery: Content Studio or Sales Outreach.
example · IT operationsenterprise

A data centre migration at a bank

Feature takes the migration request and proposes three plans: network, storage and application cutover. Each plan writes its phase files, and the go-ahead at Ready to Execute comes from the change board before any phase task starts. Feature verifies the whole cutover before it closes.

Define Plans, Ready to Execute and Verify gates

how it fits

How do the Project Planning workflows connect?

The templates nest. A feature (initiative) creates child plans and waits for them. Each plan creates child phases and waits for them. Each phase runs on its own and verifies. Task stands alone for work too small to plan. Every parent closes only after its children are completed or cancelled, then verifies the whole.

FromToHow the work moves
FeaturePlanCreate Plans makes one child plan per approved work item; Execute Plans waits until every child is finished.
PlanPhaseCreate Phases makes one child task per phase file; Execute Phases waits until every phase is finished.
FeatureTaskDefine Plans can make a small, self-contained item a direct task or bug child, with no plan wrapper.

In Project Planning, a parent step that waits on children holds until every child task is completed or cancelled.

where approval is required

Where does the Project Planning kit wait for approval?

The eight Project Planning approval gates, read from the stored workflows; each holds until an explicit approval is given.

TemplateStep with an approval gateIf you reject
FeatureDefine Plans step 2no rejection path; approve to continue
Verify step 5back to Execute Plans
PlanReview step 5back to Apply Fixes
Ready to Execute step 7no rejection path; approve to continue
Verify step 9back to Execute Phases
PhaseVerify step 3back to Implement
TaskAnalyze step 2no rejection path; approve to continue
Verify step 4back to Implement
example

What does a week with the Project Planning kit look like?

An illustrative Project Planning run, labelled as an example, using the real Project Planning step names.

  1. 01

    You ask for CSV export

    Your AI starts a Feature run. Capture checks the title, outcome and problem are clear.

  2. 02

    You approve two plans

    Define Plans proposes an export-service plan and a UI task. You approve; Create Plans makes both children.

  3. 03

    Plans become phases

    The plan drafts docs/plans/{task-slug}/ with phase files. You review it, give the go-ahead, and phase tasks appear.

  4. 04

    Phases verify, the feature closes

    Each phase verifies alone. When all children finish, Feature verifies the whole export path, and you approve the close.

what you need

What do you need to run the Project Planning kit?

make it yours

How do you customize the Project Planning kit?

Once installed, each Project Planning template is a workflow in your workspace; ask your AI to change it in plain words.

Claude Codeexample

new chat

Add a security review approval to Phase before Verify.
workflow_step_update · Project Planning
Done. Project Planning in your workspace now has the change, and every new run follows it.

more example prompts

  • "Add a security review approval to Phase before Verify."
  • "In Feature, require a one-page spec before Define Plans."
  • "Remove the Ready to Execute approval from Plan."
questions

Project Planning kit FAQ

What is the ConvOps Project Planning kit?

The ConvOps Project Planning kit gives your AI four connected workflows for delivery without strategic goals: Feature breaks an initiative into plans, Plan writes phases, Phase executes one chunk, and Task handles everything small. Parents wait for their children, and you approve the breakdown, the plan and every verification.

How is Project Planning different from Strategic Delivery?

Both are ConvOps delivery kits built on Feature, Plan and Phase. Project Planning has no Goal template and adds Task for small work, so it suits delivery run from requests. Strategic Delivery starts at a Goal with a measurable outcome and runs Feature, Plan and Phase under it, so the goal closes only after the work under it is completed or cancelled.

Do the phases run in parallel?

They can. In ConvOps each phase is its own child task with its own Phase workflow, so different agents or people can pick them up at the same time. Steps inside one workflow run in order, and the parent plan's Execute Phases step waits until every phase is completed or cancelled before the plan moves on to Verify.

Can I install Project Planning on the Free plan?

Partly. The ConvOps Free plan includes 3 workflow templates and Project Planning has 4 (Feature, Plan, Phase and Task), so the full kit needs Pro or above. Any three of them install on Free. Feature lists Plan and Phase as dependencies, so Plan, Phase and Task is the set of three whose dependencies are all installed.

How many approvals does a full run have?

In ConvOps, Feature has two approvals (Define Plans and Verify), Plan has three (Review, Ready to Execute and Verify), each Phase has one at Verify, and Task has two (Analyze and Verify). Each holds its step until an explicit approval is given, recorded with the account that gave it, and you can remove any of them as the process matures.

What does Task add to Project Planning?

In ConvOps, Task is the Project Planning route for work too small for a plan. Intake checks for a title and summary, Analyze writes a one-screen plan that holds until an explicit approval is given, Implement makes the change, and Verify checks it against the plan. A failed Verify returns to Implement, so small work gets the same check as a phase.