AugmentClaude

Plan Executor

Execute multi-phase plans by coordinating specialized subagents.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/do-thedotmack/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.

What this skill does

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)

Related skills