plan

A command that creates an implementation plan before code is written. It can guide a test-driven development (TDD) workflow, where tests are written to define expected behavior before implementation.

In plain words
What is it for?
Use it to plan features, choose an appropriate specialist, prepare a TDD-based approach, and then move from planning to execution.
Why use it?
It helps turn a coding request into clear steps and identify the work before changes are made.

Command

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 commands/jeremydev87/codingbuddy/plan
Clone the repo
git clone --depth 1 https://github.com/JeremyDev87/codingbuddy
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,264 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02264
Opus 5 $0.00000 $0.01132
Sonnet 5 $0.00000 $0.00453
Haiku 4.5 $0.00000 $0.00226

Measured 2d ago against content hash 4f815e599bca, 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.

packages/claude-code-plugin/commands/plan.md · 273 lines

How it starts

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

PLAN Mode

Purpose

Design implementation approach before writing code

Mode Availability

Standalone Mode (no MCP server)

This command works without the CodingBuddy MCP server. In standalone mode, you get:

  • Mode detection and transition
  • Basic agent recommendation
  • TDD workflow guidance
  • Core checklist

MCP Enhanced Mode

With the CodingBuddy MCP server connected, you additionally get:

  • parse_mode with full context tracking
  • Specialist agent dispatch
  • Contextual checklists (security, accessibility, performance)
  • Cross-session context persistence

Activation

Invoke via /codingbuddy:plan (namespaced) or the PLAN keyword.

Legacy bare /plan is deprecated. See Migration Guide.

This command activates PLAN mode for the CodingBuddy workflow.

Instructions

Important:

  • PLAN mode is the default starting mode
  • PLAN mode creates actionable implementation plans following TDD and augmented coding principles
  • After creating plan, user can type ACT to execute

🔴 Agent Activation (STRICT):

  • When in PLAN mode, the default PLAN agent (loaded via parse_mode in MCP mode; Technical Planner in standalone mode) MUST be automatically activated
  • The Agent's workflow framework and all mandatory requirements MUST be followed
  • In MCP mode, the agent framework is loaded via parse_mode. In standalone mode, basic workflow guidance is provided by the mode detection hook.

Purpose: Create actionable implementation plans following TDD and augmented coding principles


Clarification Phase (Optional)

Purpose: Resolve ambiguous requirements through sequential Q&A before creating a plan.

Trigger Condition:

  • AI assesses user request for ambiguity
  • If unclear scope, constraints, priority, or expected behavior detected → Start Clarification Phase
  • If requirements are already clear → Skip directly to Plan creation

Phase Rules:

  1. Single Question Rule - Ask only ONE question per message
  2. Progress Indicator - Display "Question N/M" format (estimate M, adjust as needed)
  3. Multiple-Choice First - Provide A/B/C options whenever possible
  4. Custom Input Allowed - Always allow "Other" option for user's own input
  5. Language Setting - Follow agent's communication.language setting; if not set, detect from user's input language

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

  1. 2d ago First seen · 273 lines · 0 tokens per session scan A 4f815e599bca

Subscribe to this mod's changes

plan is a command published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,264 tokens. 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-30.