From test-plan
Produce a focused, proportional test plan for the current change.
How this command is triggered — by the user, by Claude, or both
Slash command
/test-plan:test-plan [path-or-base-branch]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Produce a test plan for **$1** (default: the working diff against the repo's default branch). Steps: 1. Scope the change: `git diff $1 --stat` for breadth, then read the changed code to understand behavior — inputs, outputs, side effects, and error paths. 2. Apply the `test-design-heuristics` skill to decide *what* deserves a test and at *which* level. 3. Output a plan with: - **What to test** — the behaviors and contracts that matter, as a checklist. - **Level** — for each, unit / integration / end-to-end, with a one-line why. - **Edge cases** — boundaries, empty/null, err...
Produce a test plan for $1 (default: the working diff against the repo's default branch).
Steps:
git diff $1 --stat for breadth, then read the changed code to
understand behavior — inputs, outputs, side effects, and error paths.test-design-heuristics skill to decide what deserves a test and at which
level.Keep it proportional: a small change gets a small plan. Don't pad. This produces a plan, not the tests — offer to write them as a follow-up if the author wants.
npx claudepluginhub meaganewaller/rosetta --plugin test-plan/test-planDesigns a complete usability test plan with research questions, tasks, metrics, participant criteria, and facilitation guide for a product, feature, or prototype.
/test-planDesigns a complete usability testing plan for a product, feature, or prototype. Includes objectives, methodology, scenarios, click tests, accessibility checks, logistics, and analysis framework.
/test-planCreates a structured test plan from feature artifacts — queries test types, environment, and credentials, auto-detects the test framework, generates test cases mapped to user stories, and saves them under features/<name>/testing/.