do — Claude Code skill: what it does, how to install
The skill runs an implementation plan in phases through subagents. Use it when a plan needs execution with checks after each phase.
npx skills add thedotmack/claude-mem --skill do -a claude-codeWhat do does
The do skill acts as an orchestrator. It splits an implementation plan into phases and gives each subagent one clear objective. Every subagent must report commands run, files changed, and evidence of the result. The orchestrator coordinates the work and checks each report against the plan.
After a phase, separate subagents verify the result, look for anti-patterns, and review code quality. The process moves forward only after the current phase is confirmed. A commit subagent is used only when verification passes, while a branch and sync subagent prepares the next handoff.
The skill is available for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. Plan for verification to stop the workflow when an API or another implementation detail needs to be checked against documentation.
What it helps with
- split an implementation plan into phases
- assign focused tasks to subagents
- verify each completed phase
- check code for plan-specific anti-patterns
- prepare context for the next phase
Example prompts for the agent
- Execute this implementation plan in phases and assign each task to a subagent.
- Run every post-phase check and do not create a commit until verification passes.
- Carry out the plan from `make-plan`, recording commands, changed files, and each subagent's evidence.
How to install do
1Skills CLI (Vercel)
npx skills add thedotmack/claude-mem --skill do -a claude-code2Manually: put the files in place
~/.claude/skills/do/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/do/
1Skills CLI (Vercel)
npx skills add thedotmack/claude-mem --skill do -a codex2Manually: put the files in place
.agents/skills/do/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add thedotmack/claude-mem --skill do -a cursor2Manually: put the files in place
.cursor/skills/do/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install thedotmack/claude-mem do2Manually: put the files in place
.github/skills/do/SKILL.md1Skills CLI (Vercel)
npx skills add thedotmack/claude-mem --skill do -a gemini-cli2Platform CLI
gemini skills install https://github.com/thedotmack/claude-mem --path plugin/skills/doManually: put the files in place
.devin/skills/do/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add thedotmack/claude-mem --skill do -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set15
The whole set →Similar
Questions about do
How do I install do in Claude Code?
Run these steps in order: npx skills add thedotmack/claude-mem --skill do -a claude-code, run npx skills add thedotmack/claude-mem --skill do -a claude-code again, then use ~/.claude/skills/do/SKILL.md.
What does the do skill do?
It executes a phased implementation plan through subagents. Each phase gets verification, anti-pattern checking, and a code quality review before the workflow continues.
Which platforms support do?
The skill is available for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.
Source text
SKILL.md · Apache-2.0
--- 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 · thedotmack/claude-mem