Agent skill

Phased Plan Maker

by thedotmack in thedotmack/claude-mem

Creates a phased implementation plan that begins with documentation discovery and frames each phase to copy from docs, with verification checklists and anti-pattern guards.

Apache-2.0Auto-check passedAgent Workflows

Install Phased Plan Maker

skills CLI
$ npx skills add thedotmack/claude-mem --skill make-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thedotmack/claude-mem make-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thedotmack/claude-mem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/make-plan .claude/skills/make-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
make-plan
GitHub stars
97k
Token cost
~788 tokens
SKILL.md length
397 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
Apache-2.0

At a glance

Creates a phased implementation plan that begins with documentation discovery and frames each phase to copy from docs, with verification checklists and anti-pattern guards.

  • Works in 4 steps: Sources consulted (files/URLs) and what… → Concrete findings (exact API… → Copy-ready snippet locations (example… → …
  • Planning a feature or multi-step task before any code is written
  • SKILL.md covers Delegation Model, Plan Structure, Key Principles and Anti-Patterns to Prevent, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The agent acts as an orchestrator that writes plans meant to be executed one phase at a time in fresh chat contexts. Subagents do the fact gathering and extraction, such as documentation, examples, signatures and grep results, while the orchestrator keeps synthesis and plan authoring, and a report that lacks sources is rejected and redeployed. Each report must list sources consulted, exact findings, copy-ready snippet locations and a confidence note with known gaps.

Phase zero is always documentation discovery: find and read the relevant docs and patterns, identify the actual APIs and signatures available, create an allowed-APIs list that cites sources and note anti-patterns such as methods that do not exist. Each implementation phase then states what to implement framed as copying from docs, the documentation references, a verification checklist and anti-pattern guards.

The final phase verifies that implementations match the documentation, greps for known bad patterns and runs tests. Key principles say that documentation being available is not the same as it being used, task framing should point agents to docs, proof beats assumption, and each phase should stand alone with its own references. The plan is meant to be run next with the do skill.

When your agent uses it

  • Planning a feature or multi-step task before any code is written
  • Producing a plan that fresh sessions can execute phase by phase
  • Making sure a plan is grounded in real documentation and APIs

Example prompts

  • “Make a phased plan for adding SSO login, starting with documentation discovery.”
  • “Plan the move from REST polling to webhooks so each phase can run in a new session.”
  • “Create an implementation plan for the export feature with a verification checklist per phase.”

Requirements

  • An agent that can launch subagents

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  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)

What it can do on your machine

Read from SKILL.md and the folder at commit 71ddd11. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Phased Plan Maker loads about 788 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 397 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~788

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from thedotmack/claude-mem at commit 71ddd11, republished under its Apache-2.0 licence (© thedotmack). 397 words, ~788 tokens.

Download SKILL.mdSave it as .claude/skills/make-plan/SKILL.md (or your agent's skills folder).
name
make-plan
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.

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

Phase 0: Documentation Discovery (ALWAYS FIRST)

Before planning implementation, deploy "Documentation Discovery" subagents to:

  1. Search for and read relevant documentation, examples, and existing patterns
  2. Identify the actual APIs, methods, and signatures available (not assumed)
  3. Create a brief "Allowed APIs" list citing specific documentation sources
  4. Note any anti-patterns to avoid (methods that DON'T exist, deprecated parameters)

The orchestrator consolidates findings into a single Phase 0 output.

Each Implementation Phase Must Include
  1. What to implement — Frame tasks to COPY from docs, not transform existing code
    • Good: "Copy the V2 session pattern from docs/examples.ts:45-60"
    • Bad: "Migrate the existing code to V2"
  2. Documentation references — Cite specific files/lines for patterns to follow
  3. Verification checklist — How to prove this phase worked (tests, grep checks)
  4. Anti-pattern guards — What NOT to do (invented APIs, undocumented params)
Show full SKILL.md (140 more words)Show less
Final Phase: Verification
  1. Verify all implementations match documentation
  2. Check for anti-patterns (grep for known bad patterns)
  3. Run tests to confirm functionality

Key Principles

  • Documentation Availability ≠ Usage: Explicitly require reading docs
  • Task Framing Matters: Direct agents to docs, not just outcomes
  • Verify > Assume: Require proof, not assumptions about APIs
  • Session Boundaries: Each phase should be self-contained with its own doc references

Anti-Patterns to Prevent

  • Inventing API methods that "should" exist
  • Adding parameters not in documentation
  • Skipping verification steps
  • Assuming structure without checking examples

See Also

  • oh-my-issues — the issue-side sibling. When the plan you're being asked to make is rooted in a bug or feature backlog rather than a fresh idea, route through oh-my-issues first to cluster issues by root cause into plan masters and plans/0X-*.md design docs. make-plan then operates on the design doc for one plan slice.

© thedotmack, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugin/skills/make-plan of thedotmack/claude-mem.

Open the folder on GitHubat commit 71ddd11

Compare with similar skills

Phased Plan Maker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Phased Plan Maker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Phased Plan Maker this skillthedotmack/claude-mem97k—~788Automated safety check: PassApache-2.0
ULW Plancode-yeongyu/oh-my-openagent70k—~4.8kAutomated safety check: PassCustom licence
Execute Taskanombyte93/prd-taskmaster604—~4.8kAutomated safety check: NotesMIT
PlanEliasOulkadi/shokunin114—~1.9kAutomated safety check: PassMIT
Subagent Driven DevelopmentAsvarox/allkaraoke26137 repos~1.2kAutomated safety check: PassNone
Planning And Task Breakdownabashev/vfs-s31068 repos~1.9kAutomated safety check: PassApache-2.0

Similar skills

  • ULW Plan

    code-yeongyu/oh-my-openagent

    Acts as an explore-first planning consultant that studies the codebase and writes a single decision-complete work plan before any implementation starts.

    70k GitHub stars~4.8k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Execute Task

    anombyte93/prd-taskmaster

    Execute the next TaskMaster task using the implementation plan with CDD verification.

    604 GitHub stars~4.8k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check: notes
  • Plan

    EliasOulkadi/shokunin

    Planning agent for task breakdown and implementation planning.

    114 GitHub stars~1.9k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 37 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Breaks work into ordered tasks. An agent skill from abashev/vfs-s3.

    106 GitHub starsUsed in 8 repos~1.9k tokens
    Agent WorkflowsAuto-check passed
  • ULW Plan Workflow

    code-yeongyu/oh-my-openagent

    Explore-first planning that turns a vague or large request into one decision-complete work plan, written only after your approval and executed by a separate worker.

    70k GitHub stars~3.9k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from thedotmack/claude-mem

All 26 skills in this repo
  • Walks you through creating, installing and verifying a custom claude-mem mode, including note types, tags and optional Telegram alerts for chosen memories.

    97k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Project Timeline Report

    thedotmack/claude-mem

    Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.

    97k GitHub starsUsed in 1 repo~3.1k tokens
    Auto-check passed
  • Pull Request Babysitter

    thedotmack/claude-mem

    Keeps watching a pull request, fixing real review and CI problems and resolving stale threads, until it is clean and ready to merge.

    97k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Claude-Mem Install for Grok Bot

    thedotmack/claude-mem

    Use this when setting up claude-mem on Grok Bot: local worker plus CMEM Pro observer (default), optional host-login observer, or remote cmem.ai. No Cursor…

    97k GitHub stars~440 tokensUpdated today
    Auto-check passed
  • Claude-Mem Cloud Sync

    thedotmack/claude-mem

    Checks claude-mem cloud sync status and guides you through connecting a cmem.ai Pro account without the sync token ever passing through the chat.

    97k GitHub stars~1k tokensUpdated today
    Auto-check: notes
  • Audits a design against Dieter Rams' ten principles of good design, scores each with evidence, and hands off a make-plan prompt for a new, refined or redesigned outcome.

    97k GitHub stars~4.6k tokensUpdated today
    Auto-check passed

Categories

Questions about Phased Plan Maker

What does Phased Plan Maker do?

Creates a phased implementation plan that begins with documentation discovery and frames each phase to copy from docs, with verification checklists and anti-pattern guards. The agent acts as an orchestrator that writes plans meant to be executed one phase at a time in fresh chat contexts. Subagents do the fact gathering and extraction, such as documentation, examples, signatures and grep results, while the orchestrator keeps synthesis and plan authoring, and a report that lacks sources is rejected and redeployed.

When should I use Phased Plan Maker?

Phased Plan Maker fits situations like: planning a feature or multi-step task before any code is written; producing a plan that fresh sessions can execute phase by phase; making sure a plan is grounded in real documentation and APIs.

How do I install Phased Plan Maker in Claude Code?

Run `npx skills add thedotmack/claude-mem --skill make-plan -a claude-code`. Or copy the skill folder (plugin/skills/make-plan in thedotmack/claude-mem) into .claude/skills/make-plan in your project. Claude Code loads it when a task matches its description.

How do I install Phased Plan Maker in Codex?

Run `npx skills add thedotmack/claude-mem --skill make-plan -a codex`. Or copy the skill folder (plugin/skills/make-plan in thedotmack/claude-mem) into .agents/skills/make-plan in your project. Codex loads it when a task matches its description.

Can I use Phased Plan Maker in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedotmack/claude-mem --skill make-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/make-plan, .gemini/skills/make-plan, .github/skills/make-plan and .opencode/skills/make-plan in your project.

What does Phased Plan Maker need to run?

SKILL.md names no scripts, command-line tools or credentials: Phased Plan Maker is instructions for the agent only. Our summary lists: An agent that can launch subagents.

Does Phased Plan Maker access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Phased Plan Maker safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Phased Plan Maker use?

Phased Plan Maker is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Phased Plan Maker use?

About 788 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Phased Plan Maker?

Skills that share tags, products or a category with Phased Plan Maker: ULW Plan (code-yeongyu/oh-my-openagent, 70k stars), Execute Task (anombyte93/prd-taskmaster, 604 stars), Plan (EliasOulkadi/shokunin, 114 stars) and Subagent Driven Development (Asvarox/allkaraoke, 261 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Phased Plan Maker?

thedotmack (a GitHub user) maintains it in thedotmack/claude-mem, which has 97,250 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 7, 2026.

Source: thedotmack/claude-mem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.