do
The "do" skill orchestrates execution of multi-phase implementation plans by deploying specialized subagents for implementation, verification, anti-pattern checking, and code quality review at each phase. Use this skill when asked to execute, run, or carry out a detailed plan, particularly one previously created by the "make-plan" skill, ensuring each phase completes with verified evidence before advancing to the next step.
git clone --depth 1 https://github.com/thedotmack/claude-mem /tmp/do && cp -r /tmp/do/plugin/skills/do ~/.claude/skills/doSKILL.md
# 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)
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design audit", or asks for a critique that should lead to a plan.
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
Build and query AI-powered knowledge bases from claude-mem observations. Use when users want to create focused "brains" from their observation history, ask questions about past work patterns, or compile expertise on specific topics.
Prime a codebase by reading every source file in full. Use when starting work on a new or unfamiliar project, or when the user asks to "learn the codebase", "read the codebase", "prime", or "get up to speed".
Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.
Search claude-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.