Make Plan (Phased Implementation Planner)
Turns a feature request into a phased, doc-verified implementation plan where each phase can be executed in a fresh chat session.
Dev & CodingIntermediate★ 90,139⑂ 7,846AI score 7/10Last updated: Aug 9, 2026
What it does
Puts Claude in an orchestrator role that authors a phased implementation plan instead of diving straight into code. Three mechanics matter most:
- Mandatory Phase 0 — Documentation Discovery: subagents read real docs, examples and existing patterns to build an "Allowed APIs" list with cited sources, so the plan never depends on invented methods.
- Every phase carries four parts: what to implement (framed as copy this pattern rather than transform this code), documentation references with file/line pointers, a verification checklist, and anti-pattern guards.
- Subagent reporting contract: sources consulted, concrete findings (exact signatures/paths), copy-ready snippet locations, plus a confidence note and known gaps. Sourceless conclusions get sent back for rework.
Because each phase is self-contained with its own doc references, you can execute phase 2 tomorrow in a brand-new context.
Who it's for
- Anyone whose agent hallucinates APIs or drifts halfway through a large feature
- Developers splitting long work across multiple sessions and wanting a written plan artifact
- Teams doing SDK/library migrations where matching official docs is non-negotiable
- Workflows that separate research (subagents) from synthesis (orchestrator)
Example uses
- SDK v1 → v2 migration: Phase 0 extracts the real v2 session API from docs; later phases say "copy the pattern at docs/examples.ts:45-60" and include grep checks for deprecated calls.
- New feature design: ask for a plan for a notification center — you get separate UI, API, migration and test phases, each with a concrete proof-of-done step.
- Multi-session refactor: run Phase 1 today, open a fresh chat tomorrow and run Phase 2 with no re-explaining, since the phase embeds its own references.
· · · Install guide · · ·
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/make-plan && cp -r /tmp/claude-mem/plugin/skills/make-plan/* ~/.claude/skills/make-plan/⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal.
- Clone the repo to a temp folder:
git clone https://github.com/thedotmack/claude-mem.git /tmp/claude-mem - Create the skill folder:
mkdir -p ~/.claude/skills/make-plan - Copy the skill files:
cp -r /tmp/claude-mem/plugin/skills/make-plan/* ~/.claude/skills/make-plan/ - Confirm that
~/.claude/skills/make-plan/SKILL.mdexists. - Restart Claude Code and test with a prompt like "Use make-plan to plan the payments module refactor".
- (Optional) Save the generated plan as Markdown under your project's
plans/folder so a later session can pick up the next phase.
View source on GitHub ↗License: Apache-2.0