Skip to main content
skill Claude Code CX Codex Cursor GitHub Copilot

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.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add thedotmack/claude-mem --skill do -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/do/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/do/

From the same set15

The whole set →
mem-search thedotmack Searches memory for solutions and context from previous coding sessions when you need to recall past work. Claude Code CX Codex Cursor +1 8,900installs smart-explore thedotmack Uses tree-sitter to map code structure and find symbols. Useful when you need to explore a codebase without loading every full file. Claude Code CX Codex Cursor +1 7,300installs make-plan thedotmack Turns a feature request into a phased plan built on real documentation instead of guesses. Useful right before you run do. Claude Code CX Codex Cursor +1 7,200installs knowledge-agent thedotmack Builds focused knowledge corpora from claude-mem observations and lets you query them in an AI session. Useful for reviewing past work by topic or project. Claude Code CX Codex Cursor +1 5,700installs learn-codebase thedotmack Instructs the agent to read every source file in full before starting work. Built for onboarding on unfamiliar repositories. Claude Code CX Codex Cursor +1 5,300installs how-it-works thedotmack Explains how claude-mem works behind the scenes. It covers tool observation logging, local file storage, and memory injection timing. Claude Code CX Codex Cursor +1 5,100installs pathfinder thedotmack This skill maps feature flows, finds duplicated concerns, and proposes a unified architecture. Use it to inspect a codebase before a refactor. Claude Code CX Codex Cursor +1 5,100installs wowerpoint thedotmack Turns a single text document into a kawaii NotebookLM slide deck via CLI. Helpful when you need to render an architecture doc or report into clear, shareable slides. Claude Code CX Codex Cursor +1 4,400installs

Similar

repo-intake-and-plan lllllllama Scans a repository through its README and project files, then builds a small reproduction plan. Use it before running experiments. Claude Code CX Codex Cursor +1 474,500installs env-and-assets-bootstrap lllllllama Prepares environment and checkpoint/dataset paths before the first run of a README-documented repo. Claude Code CX Codex Cursor +1 474,300installs paperclip paperclipai Skill for AI agents running in Paperclip heartbeat loops to inspect task context, publish documents, and interact with the control plane API. Claude Code CX Codex Cursor +1 3,800installs open-source browser-use Reference guide for the browser-use open-source Python library. Helps configure Agent and Browser classes, custom tools, lifecycle hooks, and monitoring. Claude Code CX Codex Cursor +1 3,500installs openai-docs official openai The skill finds current OpenAI guidance for API work, Codex, model selection, migrations, and prompt updates, using official documentation. Claude Code CX Codex Cursor +1 6,100installs bmad-agent-pm bmad-code-org Activates John, a product manager persona for PRD creation and requirements discovery. It breaks down product ideas into deliverable tickets. Claude Code CX Codex Cursor +1 11,800installs setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. Claude Code 1,052,851installs to-tickets Matt Pocock Turns a plan, spec, or conversation into small end-to-end tickets with explicit blockers. Use it to agree on the work breakdown before tickets go to a tracker. Claude Code 711,230installs

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

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor