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

The 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 a person

the set

What's in the Project Planning kit?

Four workflow templates, installed together. Each one is a stored workflow your AI client receives one step at a time over MCP.

01 · 7 steps · 2 approvals

Feature

Deliver features from requirements to reviewed release. The AI drives through Capture, planning, execution, and Verify.

  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

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

  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

Execute an implementation phase from ready to verified. The AI drives through Ready, Implement, and Verify.

  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

Take any work item from intake to verified completion. The AI drives through Intake, Analyze, Implement, and Verify.

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

A parent step that waits on children holds until every child task is completed or cancelled. Each child runs its own workflow, and its steps run one after another.

where a person decides

Where does a person approve in the Project Planning kit?

Every approval step in the kit, read from the stored workflows. The run holds at each one until you answer.

TemplateApproval stepIf 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 run, labelled as an example. The step names are the templates' real steps.

  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?

An AI client
Claude Code, Claude (desktop, web, Cowork), OpenAI Codex, ChatGPT, Cursor, OpenCode, or any MCP client. Some steps change code, so use a coding client with your repository checked out for those runs.
ConvOps plan
The Free plan includes 3 workflow templates. This kit installs 4, so the full kit needs Pro or above. On Free, install the three you use most.
Where the work lands
Child tasks and task notes in ConvOps, plus plan files and code in your repository where a step names them.
Approvals
Eight approval steps across the kit. You answer each one in your chat; the engine records who approved.
make it yours

How do you customize the Project Planning kit?

Installed templates are workflows in your workspace. Ask your AI to change one in plain words; the edit lands on the step that needs it.

Claude Codeexample

new chat

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

How is Project Planning different from Strategic Delivery?

Project Planning has no Goal template and adds Task for small work. Strategic Delivery starts at a Goal and runs Feature, Plan and Phase under it.

Do the phases run in parallel?

Each phase is its own child task with its own workflow, so different agents or people can pick them up. Steps inside one workflow run in order; the parent plan waits until every phase is finished.

Can I install the kit on the Free plan?

The Free plan includes 3 workflow templates and this kit has 4, so the full kit needs Pro or above. You can install any three on Free.

Which AI clients can run the Project Planning kit?

Any MCP client connected to ConvOps. Verified clients: Claude Code, Claude (desktop, web, Cowork), OpenAI Codex, ChatGPT, Cursor, OpenCode. Runs that change code need a coding client with your repository checked out.