Do Plan
SkillProductivityLets your agent execute a multi-step implementation plan by delegating work to subagents.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Do Plan skill
About this capability
Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.
What this skill tells your AI
The instructions your AI receives, as published by thedotmack/claude-mem in plugin/skills/do/SKILL.md and read by ahel’s review.
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)
Signals
- GitHub stars
- 94k
- Forks
- 8k
- Last commit
- Sep 2026
Others that do the same job
Advanced
- Catalog kind
- skill
- Gateway key
do-thedotmack- Source
- github.com/thedotmack/claude-mem