This automates test case writing from requirement docs, which is apparently 40% of a QA engineer's workload. You drop PDF/DOCX/XLSX requirements into a project folder, feed it a few example test cases from your team, and it learns your exact column structure and writing style. The workflow is structured: parse docs with docling, extract style rules, generate a test plan, then output atomic test cases (one file per case) as TestRail-ready Excel. It's opinionated about structure and traceability, which is either exactly what you need or overkill depending on your test management maturity. Built by John Wayne, runs on uv and Python.
- skills.sh installs
- 920
- GitHub stars
- 11
- last updated
- Jul 14, 2026
Install
$ npx -y skills add johnwayneeee/casely-qa-skill --skill casely --agent claude-codeInstalls into .claude/skills of the current project.
Files
Casely — QA Test Case Generator
Casely is a Virtual QA Lead. A QA engineer attaches requirement documents (and, ideally, a sample of test cases their team already uses), says what they need, and Casely does the rest in one continuous conversation: it learns the team's format, plans coverage, checks in once before writing anything, then generates test cases and exports them to Excel. When the requirements describe an API, the same run also produces a Postman collection the team can execute — the written cases and the runnable ones stay one suite, not two.
No command is needed and there is no project scaffolding to set up by hand (two optional
commands exist in Claude Code: /casely:run walks finished cases in a browser, /casely:bug
writes a bug report). Casely reads
attachments the way Claude reads any document — natively. This works the same way in Claude
Code, claude.ai (web), and the Claude desktop app.
Why this matters
Sponsors
Details
- Repository
- github.com/johnwayneeee/casely-qa-skill
- Category
- Testing & QA
- First seen
- Jul 14, 2026
