A command that creates a structured test plan for a software feature, including prerequisites, scenarios, actions, and expected results.

Use it to plan happy-path and other feature tests, record their status, and prepare the services, data, and environment needed to run them.

It turns an unstructured testing request into a checklist and can keep work on a feature branch when starting from the main branch; a feature branch is a separate line of code changes.

How TheDecipherist/claude-code-mastery-project-starter-kit configures

Reuse

Borrowing it

Nothing to install: this file belongs to TheDecipherist/claude-code-mastery-project-starter-kit. 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/TheDecipherist/claude-code-mastery-project-starter-kit/main/.claude/commands/test-plan.md

Clone the repo

git clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit

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/thedecipherist/claude-code-mastery-project-starter-kit/test-plan/github.svg)](https://agentmods.dev/commands/thedecipherist/claude-code-mastery-project-starter-kit/test-plan)

Your own site

<a href="https://agentmods.dev/commands/thedecipherist/claude-code-mastery-project-starter-kit/test-plan"><img src="https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery-project-starter-kit/test-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/thedecipherist/claude-code-mastery-project-starter-kit/test-plan"><img src="https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery-project-starter-kit/test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 674 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.00008	$0.00674
Opus 5.5	$0.00003	$0.00270
Sonnet 5.5	$0.00002	$0.00135
Haiku 4.5	$0.00001	$0.00067

Measured 2mo ago against content hash 6f175cf1c2d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

test-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/test-plan.md · 119 lines

How it starts

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

Test Plan Generator

Create a structured test plan for: $ARGUMENTS

Auto-Branch (if on main)

Before creating test plan files, check the current branch:

git branch --show-current

Default behavior (auto_branch = true in claude-mastery-project.conf):

If on main or master: automatically create a feature branch and switch to it:
```
git checkout -b test/<feature-name>-plan
```
Report: "Created branch test/<feature>-plan — main stays untouched."
If already on a feature branch: proceed
If not a git repo: skip this check

To disable: Set auto_branch = false in claude-mastery-project.conf. When disabled, warn and ask the user before proceeding on main.

Template

Generate the following markdown document:

# [Feature] Test Plan

**Created:** [today's date]
**Feature:** $ARGUMENTS
**Status:** ⬜ Not Started

---

## Quick Status

Feature Area A:    ⬜ NOT TESTED
Feature Area B:    ⬜ NOT TESTED
Feature Area C:    ⬜ NOT TESTED

---

## Prerequisites

- [ ] Required services running
- [ ] Test data created
- [ ] Environment variables set

---

## Test 1: [Happy Path]

### 1.1 [Core scenario]

**Action:** [What to do]
**Expected:** [What should happen — be SPECIFIC]

| Check | Expected | Actual | Status |
|-------|----------|--------|--------|
| Response code | 200 | | ⬜ |
| Data returned | [specific shape] | | ⬜ |
| UI updated | [specific change] | | ⬜ |

---

## Test 2: [Error Cases]

### 2.1 [Invalid input]

**Action:** [What to do]
**Expected:** [Specific error message/behavior]

---

## Test 3: [Edge Cases]

### 3.1 [Empty state]
### 3.2 [Maximum values]
### 3.3 [Concurrent access]

---

## Pass/Fail Criteria

| Criteria | Pass | Fail |
|----------|------|------|
| All happy paths work | Yes | Any failure |
| Error messages shown | Yes | Silent failure |
| Data persists | Yes | Lost on refresh |

---

## Sign-Off

| Test | Tester | Date | Status |
|------|--------|------|--------|
| Test 1 | | | ⬜ |
| Test 2 | | | ⬜ |
| Test 3 | | | ⬜ |

Read the full file on GitHub · 119 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 · 119 lines · 8 tokens per session scan A 6f175cf1c2d7

Subscribe to this mod's changes

test-plan is a command published in the GitHub repository TheDecipherist/claude-code-mastery-project-starter-kit (342 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 674 once invoked, about $0.0000 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.

Testing

test-plan next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
test-planTheDecipherist/claude-code-mastery-project-starter-kit	Command	342	4mo ago	MIT	A	8	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

claude-code-mastery-project-starter-kit: Command for Claude Code