do
π―SkillCarries out a step-by-step plan by handing each piece of work to separate helper agents. After each step it checks the result, reviews the code and saves the changes to git only when the checks pass.
Installation
npx skills add thedotmack/claude-mem --skill doRun it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).
Uses skills.sh Β· Node.js 22.20+
After installing
Ask for related work and the agent uses it on its own, or call it yourself.
/doInstall by hand
Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.
Open the skill folder β- This project
.claude/skills/do/ - All projects
~/.claude/skills/do/
These paths are for Claude Code. For other tools, the command above puts it in the right place.
SKILL.md
View on GitHub β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:
- 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)
More from this repository10
Claude-Mem gives Claude Code a memory that stays after a session ends. It keeps that memory in a compressed, shorter form.
claude-mem gives Claude Code a memory that lasts between sessions. It records what Claude does while you work, saves short summaries, and shows that context automatically when you start a new session.
Searches your saved Claude-Mem memory on cmem.ai to recall what happened in earlier sessions. It answers questions like what you did last time on a project, file or decision.
Lets your AI agent explore a codebase by looking at its outline first, such as function and class names, instead of reading whole files. This saves the agent's reading budget. It uses three companion tools to search code, show a file's structure, and open only the part you need.
Helps your AI agent write a step-by-step plan before building a feature. It first checks the real documentation for what is available, then splits the work into phases. Each phase has a clear goal, examples to copy, checks to prove it works, and mistakes to avoid.
Writes a story-style report of a project's whole development history, based on the notes that claude-mem has saved over time. It needs the claude-mem background service to be running.
Automated semantic versioning and release workflow for Claude Code plugins, bumps package.json, marketplace.json, and plugin.json in lockstep, runs the build, tags the commit, creates a GitHub release, and generates changelog entries. Enforces 'nothing left uncommitted or unpushed' by running git status at the end.
Turns the notes claude-mem keeps about your past work into focused knowledge bases you can chat with. You pick notes by project, topic, file, or date, load them into a session, then ask questions about past decisions and fixes.
Reviews a design against Dieter Rams' ten principles of good design, scoring each one with evidence. It then recommends a new design, a refinement or a redesign, and writes a ready-to-use prompt for /make-plan.
Tells your AI to read every source file in your project in full before starting work, so it deeply understands the code. It uses a lot of tokens up front to save effort later.