mcpbeat

Do

thedotmack/claude-mem-do

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

512 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
89422
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/thedotmack/claude-mem --skill do

What it tells the agent to use

found in the instruction text
Task spawns other agents

The instruction itself

7 sections, as written by the author

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:

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

After Each Phase

Deploy subagents for each post-phase responsibility:

  • Run verification checklist — Deploy a "Verification" subagent to prove the phase worked
  • Anti-pattern check — Deploy an "Anti-pattern" subagent to grep for known bad patterns from the plan
  • Code quality review — Deploy a "Code Quality" subagent to review changes
  • 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)

How to use it

Copy the folder

Take thedotmack/claude-mem-do from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.