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 for Claude Code by MasonEgger/bpe-claude-code-plugin

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add MasonEgger/bpe-claude-code-plugin

Claude Code

/plugin install bpe

Made for: Claude Code.

Or install bpe, the plugin that ships this one along with the rest of its 13 skills, 3 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/masonegger/bpe-claude-code-plugin/plan/github.svg)](https://agentmods.dev/skills/masonegger/bpe-claude-code-plugin/plan)

Your own site

<a href="https://agentmods.dev/skills/masonegger/bpe-claude-code-plugin/plan"><img src="https://agentmods.dev/badge/skills/masonegger/bpe-claude-code-plugin/plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/masonegger/bpe-claude-code-plugin/plan"><img src="https://agentmods.dev/badge/skills/masonegger/bpe-claude-code-plugin/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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,792 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00027	$0.03792
Opus 5.5	$0.00011	$0.01517
Sonnet 5.5	$0.00005	$0.00758
Haiku 4.5	$0.00003	$0.00379

Measured 1mo ago against content hash 1136f751de9f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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 · 302 lines

How it starts

The opening of the file, as written. The whole thing — 302 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.
Record the archive in spec.md. Under **Shipped:** in ## Roadmap / phase log, append - <slug>: <one-line summary> (.ai-sessions/<slug>/) as the last line, taking the summary from the accomplishment.md title and its Convergence line. If the list still reads - none yet, replace that line instead of appending. If spec.md has no ## Roadmap / phase log section (a spec written before the section existed), skip this step and tell the user; do not add the section here.
Proceed to generate a fresh plan (the rest of this skill).

Read the full file on GitHub · 302 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.

1mo ago Changed · +11 lines 1136f751de9f
1mo ago Changed 44096b06348a
2mo 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 27d ago), licensed MIT. It adds 27 tokens to every session and 3,792 once invoked, about $0.0001 per session on Opus 5.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 TDD Testing

engram-testing-coverage

TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.

Gentleman-Programming/engram · 25 tokens

principle-test-behavior-not-implementation

Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.

michael-denyer/pstack-claude · 50 tokens

conductor-implement

Execute tasks from a track's implementation plan following TDD workflow.

rmyndharis/antigravity-skills · 17 tokens

tdd

This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…

glebis/claude-skills · 92 tokens

mobiai-mobile-tdd

You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.

ArisGuimera/MobiAI-Core · 38 tokens

iterative-development

TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.

alinaqi/maggy · 24 tokens