Agent skill

Phased Plan Executor

by thedotmack in thedotmack/claude-mem

Executes a phased implementation plan by acting as an orchestrator that hands each step to subagents, verifies the results and commits only after verification passes.

Apache-2.0Auto-check passedAgent Workflows

Install Phased Plan Executor

skills CLI
$ npx skills add thedotmack/claude-mem --skill do -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thedotmack/claude-mem do --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thedotmack/claude-mem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/do .claude/skills/do && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
do
GitHub stars
98k
Token cost
~508 tokens
SKILL.md length
266 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
Apache-2.0

At a glance

Executes a phased implementation plan by acting as an orchestrator that hands each step to subagents, verifies the results and commits only after verification passes.

  • Works in 4 steps: Execute the implementation as specified → COPY patterns from documentation, don't… → Cite documentation sources in code… → …
  • Carrying out a plan produced by the make-plan skill
  • SKILL.md covers Execution Protocol and Failure Modes to Prevent
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The agent acts as an orchestrator and deploys subagents for all the work, doing only coordination, context routing and checking that each subagent finished its checklist. Every subagent gets one clear objective and must return evidence, such as commands run, outputs and files changed, and the next step does not begin until the orchestrator confirms the result matches the plan.

Within each phase an implementation subagent follows the plan, copies patterns from documentation instead of inventing them, cites sources in code comments for unfamiliar APIs and stops to verify when an API seems missing. After the phase, separate subagents run the verification checklist, grep for the plan's known bad patterns, review code quality and, only if verification passed, commit.

Between phases a branch and sync subagent pushes the verified work to the working branch and prepares the handoff, so the next phase starts with fresh subagents that still have the plan's context. Failure modes it guards against include invented APIs, undocumented parameters, skipped verification and commits before verification.

When your agent uses it

  • Carrying out a plan produced by the make-plan skill
  • Running a multi-phase implementation with verification after each phase
  • Keeping the main agent as coordinator while subagents do the work

Example prompts

  • “Execute the plan in PLAN.md phase by phase using subagents.”
  • “Carry out the migration plan we just made and commit only after each phase is verified.”
  • “Run phase two of the plan with fresh subagents and report the evidence.”

Requirements

  • An agent that can launch subagents
  • A phased implementation plan

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Execute the implementation as specified
  2. COPY patterns from documentation, don't invent
  3. Cite documentation sources in code comments when using unfamiliar APIs
  4. If an API seems missing, STOP and verify — don't assume it exists

What it can do on your machine

Read from SKILL.md and the folder at commit 71ddd11. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Phased Plan Executor loads about 508 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 266 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~508

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from thedotmack/claude-mem at commit 71ddd11, republished under its Apache-2.0 licence (© thedotmack). 266 words, ~508 tokens.

Download SKILL.mdSave it as .claude/skills/do/SKILL.md (or your agent's skills folder).
name
do
description
Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.

Do Plan

You are an ORCHESTRATOR. Deploy subagents to execute all work. Do not do the work yourself except to coordinate, route context, and verify that each subagent completed its assigned checklist.

Execution Protocol

Rules
  • Each phase uses fresh subagents where noted (or when context is large/unclear)
  • Assign one clear objective per subagent and require evidence (commands run, outputs, files changed)
  • Do not advance to the next step until the assigned subagent reports completion and the orchestrator confirms it matches the plan
During Each Phase

Deploy an "Implementation" subagent to:

  1. Execute the implementation as specified
  2. COPY patterns from documentation, don't invent
  3. Cite documentation sources in code comments when using unfamiliar APIs
  4. If an API seems missing, STOP and verify — don't assume it exists
After Each Phase

Deploy subagents for each post-phase responsibility:

  1. Run verification checklist — Deploy a "Verification" subagent to prove the phase worked
  2. Anti-pattern check — Deploy an "Anti-pattern" subagent to grep for known bad patterns from the plan
  3. Code quality review — Deploy a "Code Quality" subagent to review changes
  4. Commit only if verified — Deploy a "Commit" subagent only after verification passes; otherwise, do not commit
Between Phases

Deploy a "Branch/Sync" subagent to:

  • Push to working branch after each verified phase
  • Prepare the next phase handoff so the next phase's subagents start fresh but have plan context

Failure Modes to Prevent

  • Don't invent APIs that "should" exist — verify against docs
  • Don't add undocumented parameters — copy exact signatures
  • Don't skip verification — deploy a verification subagent and run the checklist
  • Don't commit before verification passes (or without explicit orchestrator approval)

© thedotmack, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugin/skills/do of thedotmack/claude-mem.

Open the folder on GitHubat commit 71ddd11

Compare with similar skills

Phased Plan Executor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Phased Plan Executor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Phased Plan Executor this skillthedotmack/claude-mem98k—~508Automated safety check: PassApache-2.0
OMA Multi-Agent Orchestrationfirst-fluke/oh-my-agent1.3k—~4.1kAutomated safety check: PassMIT
Orchestrator WorkerTh0rgal/sandboxed.sh515—~531Automated safety check: PassNone
Plan Execution WorkflowEveryInc/compound-engineering-plugin25k—~2kAutomated safety check: PassMIT
PUA Shot Agent Personatanweai/pua20k—~3.5kAutomated safety check: PassMIT
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence

Similar skills

  • OMA Multi-Agent Orchestration

    first-fluke/oh-my-agent

    Decomposes a complex feature into tasks, dispatches parallel specialist agents with durable state, and supervises verification, QA review and retries.

    1.3k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Orchestrator Worker

    Th0rgal/sandboxed.sh

    Sets the rules for a worker agent spawned by a boss mission: stay in scope, verify before finishing, report blockers quickly and end with a clear status.

    515 GitHub stars~531 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Plan Execution Workflow

    EveryInc/compound-engineering-plugin

    Carries out a plan, spec or clear build request end to end with local verification, then hands off to shipping or returns a structured result to a caller.

    25k GitHub stars~2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Compact version of the PUA persona skill that pushes an agent to act like a high-ownership engineer, with level roles, extra-work markers and corporate-style commentary.

    20k GitHub stars~3.5k tokensUpdated 28 days ago
    Agent WorkflowsAuto-check passed
  • Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from thedotmack/claude-mem

All 26 skills in this repo
  • Walks you through creating, installing and verifying a custom claude-mem mode, including note types, tags and optional Telegram alerts for chosen memories.

    98k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Claude-Mem Cloud Sync

    thedotmack/claude-mem

    Checks claude-mem cloud sync status and guides you through connecting a cmem.ai Pro account without the sync token ever passing through the chat.

    98k GitHub starsUsed in 1 repo~1k tokens
    Auto-check: notes
  • Claude-Mem Search

    thedotmack/claude-mem

    Searches the user's persistent cross-session memory for timestamped observations synthesized from past agent sessions on cmem.ai.

    98k GitHub starsUsed in 1 repo~511 tokens
    Auto-check passed
  • Claude-Mem Cowork Pairing

    thedotmack/claude-mem

    Pairs the claude-mem Cowork plugin with a cmem.ai account by writing the sync token, user id and SyncHub URL into the plugin config without exposing the secret.

    98k GitHub starsUsed in 1 repo~659 tokens
    Auto-check passed
  • Project Timeline Report

    thedotmack/claude-mem

    Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.

    98k GitHub starsUsed in 1 repo~3.1k tokens
    Auto-check passed
  • Pull Request Babysitter

    thedotmack/claude-mem

    Keeps watching a pull request, fixing real review and CI problems and resolving stale threads, until it is clean and ready to merge.

    98k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Phased Plan Executor

What does Phased Plan Executor do?

Executes a phased implementation plan by acting as an orchestrator that hands each step to subagents, verifies the results and commits only after verification passes. The agent acts as an orchestrator and deploys subagents for all the work, doing only coordination, context routing and checking that each subagent finished its checklist. Every subagent gets one clear objective and must return evidence, such as commands run, outputs and files changed, and the next step does not begin until the orchestrator confirms the result matches the plan.

When should I use Phased Plan Executor?

Phased Plan Executor fits situations like: carrying out a plan produced by the make-plan skill; running a multi-phase implementation with verification after each phase; keeping the main agent as coordinator while subagents do the work.

How do I install Phased Plan Executor in Claude Code?

Run `npx skills add thedotmack/claude-mem --skill do -a claude-code`. Or copy the skill folder (plugin/skills/do in thedotmack/claude-mem) into .claude/skills/do in your project. Claude Code loads it when a task matches its description.

How do I install Phased Plan Executor in Codex?

Run `npx skills add thedotmack/claude-mem --skill do -a codex`. Or copy the skill folder (plugin/skills/do in thedotmack/claude-mem) into .agents/skills/do in your project. Codex loads it when a task matches its description.

Can I use Phased Plan Executor in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedotmack/claude-mem --skill do -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/do, .gemini/skills/do, .github/skills/do and .opencode/skills/do in your project.

What does Phased Plan Executor need to run?

SKILL.md names no scripts, command-line tools or credentials: Phased Plan Executor is instructions for the agent only. Our summary lists: An agent that can launch subagents; A phased implementation plan.

Does Phased Plan Executor access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Phased Plan Executor safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Phased Plan Executor use?

Phased Plan Executor is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Phased Plan Executor use?

About 508 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Phased Plan Executor?

Skills that share tags, products or a category with Phased Plan Executor: OMA Multi-Agent Orchestration (first-fluke/oh-my-agent, 1.3k stars), Orchestrator Worker (Th0rgal/sandboxed.sh, 515 stars), Plan Execution Workflow (EveryInc/compound-engineering-plugin, 25k stars) and PUA Shot Agent Persona (tanweai/pua, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Phased Plan Executor?

thedotmack (a GitHub user) maintains it in thedotmack/claude-mem, which has 97,851 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 7, 2026.

Source: thedotmack/claude-mem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.