rampstackco/claude-skills / skills/test-case-authoring
test-case-authoring
VerifiedWrite the test plan and test cases for a single work item: every acceptance criterion traced to a case, each case with test data, steps, an observable expected result, a level, and the evidence a pass must leave behind. Use this skill whenever the user wants to write test cases, a test plan, or QA notes for a ticket, plan regression tests for a bug fix, build a traceability matrix, choose between unit, integration, end-to-end, and manual tests, or charter exploratory testing for a spike. Triggers on test cases, test plan, QA notes, how do I test this, write tests for this ticket, acceptance test, regression test, traceability, test coverage for a story, exploratory testing, test charter, what should QA check, fix verification. Also triggers when the user pastes a ticket or a set of acceptance criteria and asks whether it is testable, even if they never say test plan.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 360 B |
| SKILL.md | skill md | 11.4 KB |
| references/coverage-checklist.md | markdown | 3.0 KB |
| references/example-test-plan-story.md | markdown | 7.9 KB |
| references/exploratory-charter-template.md | markdown | 2.4 KB |
| references/test-case-template.md | markdown | 3.1 KB |
| references/test-plan-template.md | markdown | 2.9 KB |
| references/traceability-matrix-template.md | markdown | 2.7 KB |
references/coverage-checklist.md
View on GitHub# Coverage Checklist
Mandatory coverage classes per ticket type, and the questions that find cases inside each class. Every mandatory class gets cases or a written "not applicable, because."
---
## Mandatory classes by type
| Class | Bug | Task | Story | Spike |
|---|---|---|---|---|
| Failing case (repro as a test) | Required | n/a | n/a | n/a |
| Happy path | If the fix changes the main flow | Required | Required | Charter |
| Boundary and edge | From QA notes | Consider | Required | Charter |
| Negative and error | From QA notes | Consider | Required | Charter |
| Regression | Required | Required | Required | n/a |
| Accessibility smoke | If user-facing | If user-facing | Required if user-facing | n/a |
| Performance smoke | If the defect was performance | Consider | Consider | n/a |
"Consider" means write cases or a one-line reason for skipping. Epics carry no cases; their stories do.
---
## Prompts per class
### Happy path
- [ ] The main flow with normal input, start to finish
- [ ] Each role that the criterion names
### Boundary and edge
- [ ] Zero, one, and many (empty list, single item, page-size plus one)
- [ ] Minimum and maximum values, and one past each
- [ ] Very long text, special characters, emoji, right-to-left text
- [ ] Time: midnight, month end, leap day, daylight saving change, time zones
- [ ] Concurrency: two users editing the same record, double submit
### Negative and error
- [ ] Invalid input: wrong format, wrong type, missing required field
- [ ] Permission boundary: a role that should not see or do this
- [ ] Dependency failure: a service down, a timeout, a slow response
- [ ] Expired state: session, link, token, cache
- [ ] The error message is specific and the user can recover
### Regression
- [ ] Every path named in the ticket's regression risk field
- [ ] Other screens or services that read or write the same data
- [ ] Existing automated suites for the area run and pass unchanged
- [ ] For a bug: the original repro no longer reproduces
### Accessibility smoke
- [ ] Every new control reachable and operable by keyboard alone
- [ ] Focus is visible and moves in a logical order
- [ ] Inputs and controls have accessible names
- [ ] State changes (errors, loading, success) are announced to a screen reader
- [ ] Text and controls meet WCAG AA contrast
This is a smoke check per item. A full audit belongs to `accessibility-audit`.
### Performance smoke
- [ ] The flow with realistic data volume (not an empty fixture)
- [ ] Response or render time within the team's budget
- [ ] No new request inside a loop, no unbounded query
This is a smoke check per item. Deeper investigation belongs to `performance-optimization`.
---
## Before calling coverage done
- [ ] Every mandatory class for the type has cases or a written reason
- [ ] Every edge case in the ticket's QA notes has a case
- [ ] Every risk in the ticket's regression risk field has a case
- [ ] Every user-facing story has at least one accessibility smoke case
- [ ] The traceability matrix shows no untraced cases
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |