make-plan (Phased Implementation Planner)

What it does

Puts Claude in an orchestrator role to author implementation plans broken into self-contained phases.

• Phase 0 — Documentation Discovery (always first): subagents read real docs, examples and existing patterns, then produce an "Allowed APIs" list with cited sources plus anti-patterns to avoid.
• Each implementation phase: what to build, which file/lines to copy the pattern from, a verification checklist (tests, grep checks), and explicit guards against invented APIs or undocumented params.
• Final phase — Verification: confirm the code matches the docs, grep for known bad patterns, run tests.

Subagents must report sources consulted, exact API signatures and file paths, copy-ready snippet locations, and a confidence note with known gaps. Conclusions without sources are rejected and the subagent is redeployed.

Who it's for

• Developers burned by hallucinated APIs that "should" exist
• Anyone splitting a large task across multiple sessions who needs each step to stand alone
• Tech leads who want implementation work anchored to official documentation

Examples

1. SDK migration: ask it to plan a move to the V2 session API — it reads the SDK docs first, pins down methods that actually exist, and frames the task as "copy the V2 session pattern from docs/examples.ts:45-60".
2. New feature: planning a payment webhook, Phase 0 greps existing handlers for the house pattern and every phase ships with a verification checklist.
3. From bug backlog to plan: run oh-my-issues first to cluster issues by root cause into design docs, then hand one slice to make-plan to turn it into an executable plan.

Install the skill I found on Claude Skill Mart.
Copy the openclaw/skills/make-plan folder from the GitHub repo thedotmack/claude-mem into my ~/.claude/skills/make-plan/.
When it's done, tell me in one line what this skill can do.