Skip to content

Do Plan Orchestrator

Runs a phased implementation plan by delegating each step to verified subagents.

Stars
110,174
Licence
Apache-2.0
Files
1 file

What it does

When you ask the agent to carry out a plan (often one made by a companion make-plan skill), this skill makes it act as a coordinator. It hands each phase's work to separate helper agents, asks them to prove what they did, runs separate checks for verification, anti-patterns and code quality, and only commits code after verification passes. It also pushes to a working branch after each verified phase.

Great for

  • Developers who have a multi-phase implementation plan and want it executed in disciplined, checked steps
  • Teams using Claude Code who want evidence-backed progress reports rather than unverified claims

Skip it if

  • Simple one-off edits, where the overhead of many subagents and commits is unnecessary
  • Work on production or shared branches without review, because the skill commits and pushes on its own once checks pass; the reason is that these actions change repository history

Try asking

  • “Execute the phased plan in plan.md one phase at a time”
  • “Carry out the implementation plan we made earlier, verifying each phase before committing”
  • “Run this plan from make-plan and push each verified phase to the working branch”
Step-by-step guide: how to use Do Plan OrchestratorInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the Apache-2.0 licence and an attribution note.

    do.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip do.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip do.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Start with a clear, phased plan file so the orchestrator has explicit checklists to verify against
  • Use a dedicated working branch so automatic commits and pushes stay isolated and easy to review
  • Check the verification evidence reported after each phase before letting later phases proceed

What's inside

  • SKILL.md

Redistributed unmodified from thedotmack/claude-mem under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.