Test Case Generator
Turn requirements into traceable test cases using boundary, partition, decision-table, and state techniques, with a coverage matrix.
Before & after
Same prompt, same agent — the only difference is the skill.
Team workflows are really important! You'll want to think about how tasks flow through your team, who owns what, and how you communicate status. Clear checklists help, and regular check-ins are good. You might want to consider whether everyone understands priorities the same way. Automation can help too—maybe some tools to track what's in progress. It depends on your team size and the types of tasks you're doing. Would you like to brainstorm what a typical task looks like from start to finish? That could help us figure out what process would work best.
TC WORKFLOW STRUCTURE PHASE 1 INTAKE • Task initiated with: owner, deadline, dependencies • Priority scored (high/medium/low) based on impact + urgency matrix • Assigned to sprint or backlog queue PHASE 2 EXECUTION • Owner posts daily checkpoint (blockers, progress %) • If blocked → escalate or swap task owner • Status visible in shared log (not buried in Slack) PHASE 3 COMPLETION • Owner submits deliverable with checklist proof • Review step: does it match acceptance criteria? • If not → return to Phase 2 with feedback loop PHASE 4 CLOSURE • Task marked done, blockers logged as lessons learned • Team reflects: Did estimates match reality? Any process friction? • Update workflow template based on actual throughput VALIDATION RULES • No task stays blocked >4 hours without escalation • Estimates vs actual time tracked per task type • Cadence: daily intake, weekly retrospective
About this skill
Test cases designed the way an experienced QA engineer does it: derived from requirements with named techniques, so coverage is systematic and every gap in the spec becomes a question instead of a guess.
What it does
- Splits requirements into testable, ambiguous, and implicit ones
- Applies equivalence partitions, boundary values, decision tables, state transitions, and pairwise coverage
- Adds the edge cases hand-written lists miss: time zones, duplicates, concurrency, cross-tenant access, expired tokens, interruptions
- Prioritizes by business impact and marks smoke and regression subsets
- Flags every expected result the spec does not define
What you get
A test case table with IDs, techniques, steps, expected results, and priorities, a requirement coverage matrix, and open questions to resolve before sign-off.
Best for
QA engineers, developers writing their own tests, and product teams checking a ticket is ready to test.
SKILL.md preview
---
name: test-case-generator
… (sign up to view the full skill)More development skills
View all Development skills →React and Next.js Regression Test Coverage
Generate React and Next.js tests with Jest, Testing Library, MSW, and Playwright, prioritized by regression risk.
Playwright E2E Tests and Flake Repair
Build reliable Playwright tests, repair flakes from evidence, migrate suites, and configure faster, diagnosable CI.
Pre-Ship Verification for Code Changes
Before calling a code change done, Claude grades every claim by evidence, tries to break it, and reports what's verified vs assumed.
TestRail Case and CI Result Sync
Sync automated tests to TestRail cases and scoped runs with stable mappings, retry handling, and verified result counts.