# Make an Implementation Plan

Writes a phased plan with documentation discovery before any work starts.

- Repository: https://github.com/thedotmack/claude-mem (109099 stars)
- Category: Business
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add thedotmack/claude-mem --skill make-plan -g -a claude-code -y`
Codex: `npx skills add thedotmack/claude-mem --skill make-plan -g -a codex -y`
Cursor: `npx skills add thedotmack/claude-mem --skill make-plan -g -a cursor -y`
Gemini CLI: `npx skills add thedotmack/claude-mem --skill make-plan -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add thedotmack/claude-mem`

## Description

Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation, especially before executing with do.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Make Plan

You are an ORCHESTRATOR. Create an LLM-friendly plan in phases that can be executed consecutively in new chat contexts.

## Delegation Model

Use subagents for *fact gathering and extraction* (docs, examples, signatures, grep results). Keep *synthesis and plan authoring* with the orchestrator (phase boundaries, task framing, final wording). If a subagent report is incomplete or lacks evidence, re-check with targeted reads/greps before finalizing.

### Subagent Reporting Contract (MANDATORY)

Each subagent response must include:
1. Sources consulted (files/URLs) and what was read
2. Concrete findings (exact API names/signatures; exact file paths/locations)
3. Copy-ready snippet locations (example files/sections to copy)
4. "Confidence" note + known gaps (what might still be missing)

Reject and redeploy the subagent if it reports conclusions without sources.

## Plan Structure

### Primary Goal (top of the document, before Phase 0)

Every plan opens with a **Primary goal** section: one or two sentences describing the *user-visible outcome* the plan exists to produce, not the mechanism. Write it so a reader with no context knows what "done" looks like.

- Good: "A paying user whose observer stops working finds out within one session and is told the one thing to do about it."
- Bad: "Add a 6-code error taxonomy to the gateway."

Then, directly under **every phase title** (Phase 0 through the final verification phase), add a short paragraph:

> **How this serves the primary goal:** …

If you cannot write that paragraph honestly for a phase, the phase does not belong in the plan. This is the scope test.

### Phase 0: Documentation Discovery (ALWAYS FIRST)

The rest: https://github.com/thedotmack/claude-mem/blob/HEAD/plugin/skills/make-plan/SKILL.md