A planning tool that turns a project specification in `spec.md` into an implementation roadmap in `plan.md` and a checklist in `todo.md`. It separates TDD feature steps—write a failing test, then code—from other development tasks.

Use it to create a fresh development plan, track completed work, and regenerate or archive an existing plan when the specification changes.

It removes the need to break a written idea into coding steps by hand. It also prevents accidentally replacing an existing plan unless you explicitly archive or regenerate it.

plan — Skill by MasonEgger

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/masonegger/bpe-claude-code-plugin/plan

Any agent

npx skills add MasonEgger/bpe-claude-code-plugin --skill plan

Clone the repo

git clone --depth 1 https://github.com/MasonEgger/bpe-claude-code-plugin

Made for: Claude Code, Codex.

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,494 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00027	$0.03494
Opus 5	$0.00014	$0.01747
Sonnet 5	$0.00005	$0.00699
Haiku 4.5	$0.00003	$0.00349

Measured 2d ago against content hash f15beea9eb7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

bpe/skills/plan/SKILL.md · 291 lines

How it starts

The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan Command

Flag handling

Run this check before anything else in this skill, including Tool discovery.

Check for plan.md at the repo root.
plan.md absent: proceed with the rest of this skill and generate a fresh plan. --archive and --regen are no-ops in this case.
plan.md present and neither --archive nor --regen in $ARGUMENTS: refuse and stop. Report in this shape:

plan.md exists (last modified , N/M items checked). Use --archive to preserve it in .ai-sessions before regenerating, or --regen to discard and regenerate.

Fill <date> from the file's modification time (date -r plan.md +%Y-%m-%d). Fill N/M from todo.md's top-level checkbox counts: N is the checked count, M the total. If todo.md is missing, write "no todo.md" in place of "N/M items checked".
plan.md present and --archive in $ARGUMENTS: run the Archive routine below, then proceed to generate a fresh plan.
plan.md present and --regen in $ARGUMENTS: delete plan.md and todo.md at the repo root (rm -f plan.md todo.md), then proceed to generate a fresh plan.

Archive routine

Referenced by the --archive flag above and by /bpe:session-summary's end-of-goal archive prompt. The archive layout and the accomplishment.md format are canonically documented in ${CLAUDE_PLUGIN_ROOT}/references/session-management.md under "Plan Archives (accomplishment.md)"; read that section before step 5 below.

Propose a slug for the archive directory based on plan.md's stated goals and the checked items in todo.md. Same 2-3 word kebab-case shape as session-summary slugs (e.g. add-user-auth); use init or v1 when the plan has no sharper focus, such as a project's first archive. Ask the user to confirm or edit the slug. Do not touch any files until the user answers.
mkdir -p .ai-sessions/<slug>/
mv plan.md .ai-sessions/<slug>/plan.md
mv todo.md .ai-sessions/<slug>/todo.md
Write .ai-sessions/<slug>/accomplishment.md following the accomplishment.md template in session-management.md. Populate it from the just-moved plan.md and todo.md plus git log commit subjects; the template section documents each field.
Proceed to generate a fresh plan (the rest of this skill).

Read the full file on GitHub · 291 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 291 lines · 27 tokens per session scan A f15beea9eb7e

Subscribe to this mod's changes

plan is a skill published in the GitHub repository MasonEgger/bpe-claude-code-plugin (7 stars, last pushed 10d ago), licensed MIT. It adds 27 tokens to every session and 3,494 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning Productivity Testing

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens