testland/test-case-ideation-from-story
Takes a user story or feature spec and emits a markdown test-case matrix - one row per case (id, title, precondition, steps, expected, tier) covering happy path, alternate paths, boundaries, and negative paths - before any test code is written. Output is the human-reviewable matrix that goes into TestRail / Qase / Xray. Emits the human-reviewable case matrix itself - not Gherkin scenarios written against locked acceptance criteria, and not executable test code. Use as the first artifact a manual tester or three-amigos session produces from a story, ahead of automation.
92
Quality
92%
Does it follow best practices?
Impact
—
Average score across 10 eval scenarios
Securityby
Low
Low-risk findings worth noting
Evaluation results
Failed
Checkout incidents all happen between page load and payment
Failed
Clinic booking rules keep failing exactly at their own limits
Failed
Evidence upload spec is mostly a list of file formats
Failed
Folder sharing: we only ever test it with a colleague who is sitting there
Failed
Invoice rendering is only ever checked in English and dollars
Failed
Nobody can tell which search cases to re-run when an AC changes
Failed
Refund console keeps shipping bugs in rule combinations nobody tried
Failed
The onboarding test list is just the click-through with a table around it
Failed
We cannot demonstrate what "delete my account" actually did
Failed
Weekly digest story is going into the sprint on Monday
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6