Do
Orchestrate every step of an approved phased plan by delegating implementation, verification, anti-pattern grep, and gated commits to fresh subagents instead of doing the work inline.
Install
npx skills add https://github.com/thedotmack/claude-mem --skill doWhat is this skill?
- Orchestrator-only role: coordinate subagents; do not implement except routing and completion checks
- Per-phase Implementation subagent with doc-copy discipline and stop-if-API-missing rule
- Post-phase Verification, Anti-pattern, and Code Quality subagents before any Commit subagent
- No advance until subagent evidence matches the plan checklist
- Fresh subagents per phase when context is large or objectives blur
Adoption & trust: 3.1k installs on skills.sh; 81.2k GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Agent Browservercel-labs/agent-browser
Lark Imlarksuite/cli
Lark Calendarlarksuite/cli
Lark Sheetslarksuite/cli
Lark Vclarksuite/cli
Lark Contactlarksuite/cli
Journey fit
Primary fit
PM subphase is where written plans become executed workstreams; Do is the orchestration counterpart to plan authoring. Focus is checklist execution and phase gates from a spec—not greenfield brainstorming or market validation.
Common Questions / FAQ
Is Do safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Do
# 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)