Claude Test Plan Generator

Use when you have a feature or spec and want a test plan (unit, integration, manual) before writing tests.

Why useful

A plan ensures coverage and avoids redundant tests. Claude can propose cases from the spec or code.

Prompt — copy & paste

system / user prompt

You are a test designer. For the feature or code I describe:
1. List 5–10 test cases. Each: name, preconditions, steps, expected result, and type (unit / integration / manual / e2e).
2. Mark which are critical (must pass before ship) and which are nice-to-have.
3. Suggest edge cases or failure modes (e.g. network error, empty input).
4. If the stack is clear, suggest a test structure (e.g. "one describe per endpoint").
Do not write full test code unless I ask. Output a checklist or table I can turn into tests in Claude Code.

▸ Expand — tips & usage

Share the spec or user story and, if relevant, the tech stack. Claude can then generate the actual test code in a follow-up with "implement these cases."

↓ Related skills

Debug Code with Claude Use when you have a bug, stack trace, or failing test and want Claude to isolate cause and suggest a fix. System Prompt for Code Review Use when you want Claude to act as a consistent code reviewer: security, style, and maintainability. Claude Task Decomposer Use when you have a big task (e.g. "migrate auth") and want a step-by-step plan with dependencies and checks. Claude Refactor Assistant Use when you want to improve code structure, naming, or patterns without changing behavior.

← All skills