do
Scannednpx machina-cli add skill thedotmack/claude-mem/do --openclawDo 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)
Source
git clone https://github.com/thedotmack/claude-mem/blob/main/plugin/skills/do/SKILL.mdView on GitHub Overview
Do is an orchestration skill that deploys subagents to execute a phased plan. It coordinates context, routes information, and verifies completion against the plan rather than doing the work itself. This approach ensures reproducibility, traceability, and strict adherence to documented practices, especially for plans created by make-plan.
How This Skill Works
Per phase, deploy an Implementation subagent to execute tasks exactly as documented, copying patterns from the source and citing APIs in code comments. After a phase, deploy Verification, Anti-pattern, and Code Quality subagents to prove success and catch issues; only commit if verification passes. Between phases, use a Branch/Sync subagent to push changes and prep the next phase handoff.
When to Use It
- Executing a multi-phase plan created by make-plan.
- Coordinating specialized subagents to complete complex tasks.
- Verifying phase results before advancing to the next step.
- Copying patterns from documentation and citing sources for APIs.
- Branching and handoffs between phases to prep the next work.
Quick Start
- Step 1: Define the plan phases and assign a single objective per subagent.
- Step 2: For each phase, deploy Implementation; collect evidence and confirm completion.
- Step 3: Run post-phase checks (Verification, Anti-pattern, Code Quality), branch and prepare the next phase; commit only if all checks pass.
Best Practices
- Define a single clear objective for every subagent.
- Require concrete evidence of completion (commands, outputs, files).
- After each phase, run Verification, Anti-pattern, and Code Quality checks.
- Only commit after verification passes; push branches between phases.
- Don’t skip verification or invent undocumented APIs.
Example Use Cases
- Orchestrating a feature rollout by executing phased tasks with Implementation, Verification, and Commit steps.
- Running a data migration plan with subagents to verify data integrity after each phase.
- Coordinating a UI rebuild by distributing tasks to subagents and validating visuals and accessibility.
- Integrating an external API by following docs, reacting to missing endpoints, and verifying changes before commit.
- Deploying security patches with phased checks and code-quality reviews prior to merge.
