Phased Implementation Planner (make-plan)
Turns a feature request into a phased, doc-grounded implementation plan that survives fresh chat contexts.
Dev & CodingIntermediate★ 92,898⑂ 8,168AI score 7/10Last updated: Sep 1, 2026
What it does
- Puts Claude in an orchestrator role: it authors the plan while subagents do fact-gathering (docs, signatures, grep results).
- Phase 0 is always documentation discovery — subagents read real docs and existing patterns and produce an "Allowed APIs" list with citations, plus anti-patterns (methods that don't actually exist, deprecated params).
- Enforces a subagent reporting contract: sources consulted, exact API names/signatures and file paths, copy-ready snippet locations, confidence note and known gaps. Source-less conclusions are rejected and redeployed.
- Every implementation phase carries: what to build (framed as copy from docs, not "transform the old code"), doc references with file/line, a verification checklist (tests, grep), and anti-pattern guards.
- A final verification phase confirms the code matches the docs, greps for bad patterns, and runs tests.
Who it's for
- Developers splitting long work across multiple sessions who keep losing context.
- Anyone tired of the model inventing API methods or parameters.
- Tech leads who want a reviewable plan document before implementation starts.
Example uses
- "Plan the payment webhook handler" → Phase 0 reads the SDK docs and existing handlers, then phases split into route, signature verification, retry handling, and verification.
- "Plan the session API V2 upgrade" → tasks are rewritten as "copy the V2 session pattern from docs/examples.ts:45-60" instead of a vague "migrate existing code".
- Take the finished plan, open a brand-new chat, and execute only Phase 1 — each phase is self-contained with its own doc references.
· · · Install guide · · ·
Try it now, no install
Paste this into Claude to use the skill without installing anything.
Read the instructions in this file and follow them to help me: https://raw.githubusercontent.com/thedotmack/claude-mem/HEAD/plugin/skills/make-plan/SKILL.md What I want: (describe your task here)
If Claude can't open the link, open it yourself and paste the contents instead.
↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the plugin/skills/make-plan folder from the GitHub repo thedotmack/claude-mem into my ~/.claude/skills/thedotmack-make-plan/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/thedotmack/claude-mem.git /tmp/claude-mem && mkdir -p ~/.claude/skills && cp -r /tmp/claude-mem/plugin/skills/make-plan ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal.
- Clone the repo:
git clone https://github.com/thedotmack/claude-mem.git /tmp/claude-mem - Make sure the skills folder exists:
mkdir -p ~/.claude/skills - Copy just this skill:
cp -r /tmp/claude-mem/plugin/skills/make-plan ~/.claude/skills/ - Verify that
~/.claude/skills/make-plan/SKILL.mdis present. - Restart Claude Code and ask something like "plan the implementation of this feature" to trigger it.
- (Optional) Also copy the
oh-my-issuesskill from the same repo if you want to plan from a bug/feature backlog.
View source on GitHub ↗License: Apache-2.0