A development-planning command hub for deciding how to approach coding work. TDD, or test-driven development, means writing tests before the implementation and then improving the code in small steps.

Use it to plan a feature or enhancement, refactor code without changing its behavior, write tests first, or review code for quality, security, and good practices.

It helps turn an unclear coding task into a structured plan or review approach before changes are made.

How Smart-AI-Memory/empathy-framework configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Smart-AI-Memory/empathy-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Smart-AI-Memory/empathy-framework/main/.claude/commands/plan.md

Clone the repo

git clone --depth 1 https://github.com/Smart-AI-Memory/empathy-framework

Made for: Claude Code.

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/commands/smart-ai-memory/empathy-framework/plan/github.svg)](https://agentmods.dev/commands/smart-ai-memory/empathy-framework/plan)

Your own site

<a href="https://agentmods.dev/commands/smart-ai-memory/empathy-framework/plan"><img src="https://agentmods.dev/badge/commands/smart-ai-memory/empathy-framework/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/commands/smart-ai-memory/empathy-framework/plan"><img src="https://agentmods.dev/badge/commands/smart-ai-memory/empathy-framework/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,765 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.00018	$0.01765
Opus 5.5	$0.00007	$0.00706
Sonnet 5.5	$0.00004	$0.00353
Haiku 4.5	$0.00002	$0.00177

Measured 2mo ago against content hash 20384785638a, 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 2mo 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.

.claude/commands/plan.md · 285 lines

How it starts

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

Development Planning

Aliases: /approach

Structured approaches for common development tasks with Socratic guidance.

Quick Examples

/plan                      # Interactive menu
/plan "auth feature"       # Start planning a feature
/plan "refactor utils"     # Plan a refactoring

Discovery

Question:
  header: "Approach"
  question: "What development approach do you need?"
  options:
    - label: "Plan implementation"
      description: "Create a plan with Socratic discovery before coding"
    - label: "Test-driven development"
      description: "Write tests first, then implement (Red-Green-Refactor)"
    - label: "Code review"
      description: "Review code for quality, security, and best practices"
    - label: "Refactor code"
      description: "Restructure code without changing behavior"

Plan Implementation

Create a plan with structured Socratic discovery before coding.

Step 1: Understand the Change

Question:
  header: "Change Type"
  question: "What kind of change are you planning?"
  options:
    - label: "New feature"
      description: "Adding entirely new functionality"
    - label: "Enhancement"
      description: "Improving or extending existing functionality"
    - label: "Bug fix"
      description: "Correcting broken behavior"
    - label: "Refactor"
      description: "Restructuring without changing behavior"

Step 2: Clarify Constraints

Question:
  header: "Constraints"
  question: "What constraints should I consider?"
  multiSelect: true
  options:
    - label: "Backward compatible"
      description: "Must not break existing APIs or behavior"
    - label: "Performance critical"
      description: "Speed or memory usage is important"
    - label: "Security sensitive"
      description: "Handles auth, user data, or system access"
    - label: "Minimal changes"
      description: "Prefer smallest possible footprint"

Step 3: Socratic Exploration

After reading the codebase, I'll ask clarifying questions like:

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

2mo ago First seen · 285 lines · 18 tokens per session scan A 20384785638a

Subscribe to this mod's changes

plan is a command published in the GitHub repository Smart-AI-Memory/empathy-framework (13 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,765 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-30.

Claude Code Planning TDD Testing ai ai-collaboration anthropic artificial-intelligence code-analysis development hub refactor review

empathy-framework: Command for Claude Code