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/traceability-matrix-template.md
View on GitHub# Traceability Matrix Template
The matrix proves two things: every acceptance criterion has a test, and every test has a reason to exist. Build it after writing cases and before calling the plan done.
---
## Template
```
TRACEABILITY: [ticket ID and title]
| Criterion or risk | Text (short) | Cases | Levels | Status |
|---|---|---|---|---|
| AC-1 | [short paraphrase] | TC-01, TC-02 | unit, e2e | covered |
| AC-2 | [short paraphrase] | TC-03 | integration | covered |
| AC-3 | [short paraphrase] | none | | GAP: not testable as written |
| RISK: [name] | [what could break] | TC-08 | integration | covered |
```
Status values: `covered`, `partial` (some sub-condition untested, name it), `GAP` (no case, with the reason), `untestable` (with what would make it testable), `deferred` (with owner and date).
---
## Reverse check: cases to criteria
```
| Case | Traces to | Class |
|---|---|---|
| TC-01 | AC-1 | happy path |
| TC-02 | AC-1 | boundary and edge |
| TC-03 | AC-2 | happy path |
| TC-08 | RISK: [name] | regression |
```
Every case appears once. Every case has exactly one trace. A case that traces to nothing is either a missing risk (name it and add a risk row) or noise (cut it).
---
## Gap checks
Run these before the plan is done.
- [ ] Every acceptance criterion has at least one case, or a status of GAP, untestable, or deferred with a reason
- [ ] Every case traces to exactly one criterion or one named risk
- [ ] No criterion is covered only by a manual case when a lower level could observe it
- [ ] Every risk from the ticket's regression risk field has a row
- [ ] Every GAP has a proposed rewrite of the criterion sent back to the ticket author
---
## Handling a gap
A GAP row is useful output, not a failure of the plan. It means the criterion needs to change before anyone can say it is done.
| Criterion as written | Why it is a gap | Proposed rewrite |
|---|---|---|
| "Search is fast" | No threshold, no data size | "Given 10,000 records, when the user types 3 characters, then results render within 1 second" |
| "Users will love the new layout" | Not observable at test time | Move to a post-launch metric on the epic; drop from the story's criteria |
| "Works on all devices" | Unbounded | "Given viewports of 375px, 768px, and 1440px, the page has no horizontal scroll" |
Send the rewrite to the ticket author. The criterion is theirs to change.
---
## For bugs
The matrix for a bug is short:
| Row | Cases |
|---|---|
| REPRO: [the failing behavior] | TC-01 (fails before the fix, passes after) |
| QA NOTE: [each edge case listed on the ticket] | TC-02 to TC-0n |
| RISK: [each shared path from regression risk] | TC-.. |
The repro case is the one named in the ticket's fix verification method.
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 |