Generates linked QA user stories and test cases from project documentation.
npx skills add https://github.com/andrewnovykov/total-66 --skill qa-andrewnovykov
Please help me install this Agent Skill. Skill: qa Source: https://github.com/andrewnovykov/total-66/tree/main/.claude/skills/qa Command: npx skills add https://github.com/andrewnovykov/total-66 --skill qa-andrewnovykov
Manages the overhead of QA documentation by converting scattered project requirements into structured, traceable QA artifacts (user stories and test cases).
Run the QA Documentation Generator against your repository to produce linked QA user stories and test cases from project documentation.
High-intent search queries and answers about installing and using this skill.
To auto-generate QA test cases and user stories, this Skill analyzes project/ and project_doc/ directories to extract requirements and outputs structured QA artifacts with bidirectional linking.
Yes, you can generate QA documentation for a specific feature by using the command syntax /qa [feature], which filters the requirement extraction to produce targeted user stories and test cases.
Bidirectional linking connects generated user stories to their corresponding test cases and vice versa, enforcing traceability rules so every requirement maps directly to its validation artifacts.
The best way to convert scattered requirements into structured QA artifacts is to run the automated generator against your repository, which reads project specifications and outputs linked user stories and test cases.
No external dependencies are required to automate QA documentation generation, as the Skill operates independently to read project specifications and produce the qa/USER-STORY/ and qa/Test-Case/ file structures.
estaciolimaGenerate structured feature specifications from natural language descriptions.
tapanshahSynchronize Playwright test results with TestRail test runs.
modalalaLink ABAP objects to Git repositories and manage repo-level operations via CLI.
mahg-esGenerate traceable test cases from requirements and user stories.
