qa-cases
Skill0 starsChanged 28 days agoMITView on GitHub
Generate complete, traceable test cases for a requirement, story, UI or API using formal techniques (EP, BVA, decision tables, state transitions, pairwise, error guessing). Supports table, Gherkin and CSV (TestRail/Xray/Zephyr) output.
In this repository10 other files it gives its agents.
- qa-auditSkill
- qa-automateSkill
- qa-bugSkill
- qa-diffSkill
- qa-exploreSkill
- qa-flakySkill
- qa-initSkill
- qa-planSkill
- qa-releaseSkill
- qaSkill
The file
Files
Delegate to the qa-test-designer subagent (it may appear as argus-qa:qa-test-designer).
Brief it with:
- Input: $ARGUMENTS (read any referenced files, tickets or existing test plans in
.qa/reports/) - Format: the table by default. If
--gherkinis present, also produce a.featurefile. If--csvis present, write.qa/testcases/<slug>.csv. - The facts from
.qa/context.mdabout roles, data and environments.
Show the user the coverage summary, the P1 cases, and any 🧠 assumed expectations that need confirmation. Offer /qa-automate for the automatable P1 cases.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.