manual-test-planlisted
Install: claude install-skill JBSommeling/claude-config
# Manual Test Plan
Generate a manual testing plan grounded in the actual diff on the current branch. Output is a single markdown file a QA engineer can execute without asking the developer questions.
## Workflow
Follow phases in order. Do not skip.
### Phase 1 — Ask change scope
Ask which scope to plan against:
1. Branch diff vs main (`git diff main...HEAD`)
2. Uncommitted changes only (staged + unstaged)
3. Branch + uncommitted
4. Specific commit range (`<base>..<head>`)
5. Last commit (`git diff HEAD~1..HEAD`)
Wait for the answer.
### Phase 2 — Read the diff (delegate to `reader`)
Delegate to the `reader` agent. Pass the exact git command. Ask for:
- One-line summary per changed file (new endpoint, modified schema, added migration, etc.)
- Test-surface signals: new routes, new env vars, new migrations, new/changed events, changed validation, modified auth, new feature flags, new CLI flags, modified response shapes
- Structured summary under 400 words — never raw diff
### Phase 3 — Ask about tools
Ask which tools are available. Default catalog:
- **Browser** + DevTools
- **API client** (curl / Postman / HTTPie / Bruno — which?)
- **CLI / shell** (which binaries?)
- **Database client** (psql / mysql / TablePlus — which DB?)
- **Event/queue inspector** (Kafka UI / SQS console / webhook.site / ngrok)
- **Logs / observability** (tail / Datadog / Grafana / Sentry)
- **Anything else?** — catch project-specific tools (Stripe CLI, AWS CLI, kubectl, flag dashboards)
### Ph