Generate structured QA test plans for game development sprints.
npx skills add https://github.com/MichaelSolati/mkai --skill qa-plan-michaelsolati
Please help me install this Agent Skill. Skill: qa-plan Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/qa-plan Command: npx skills add https://github.com/MichaelSolati/mkai --skill qa-plan-michaelsolati
This Skill solves the common issue of teams creating QA plans after feature implementation, which leads to missed test coverage, unclear testing requirements, and gaps in automated and manual verification for game development projects.
Use the qa-plan skill to generate a complete QA test plan for your current game development sprint, including all required automated tests, manual checks, and playtest requirements.
High-intent search queries and answers about installing and using this skill.
Generating a QA test plan for a game development sprint involves processing in-scope story files, game design documents, and architecture manifests to classify stories by test type and produce automated test specifications, manual verification checklists, and playtest sign-off requirements.
Story classification in game dev QA planning automatically categorizes in-scope stories by test type—Logic, Integration, Visual/UI, or Config/Data—using acceptance criteria and game design document references, or it respects pre-declared types set by lead programmers.
Preventing post-implementation testing gaps requires generating a structured QA test plan upfront before feature implementation begins, ensuring developers know exact automated test, manual verification, and smoke test requirements ahead of time.
Yes, you can use acceptance criteria and game design document references to define manual verification checklists, smoke test scopes, and playtest sign-off requirements by classifying stories into appropriate test types during sprint planning.
Yes, automated test generation respects pre-declared story types set by lead programmers, using those classifications to define specific automated test specifications and sprint-level definition of done criteria without overriding existing declarations.
The best way to structure smoke test scope and definition of done for game sprints is generating a comprehensive QA plan that processes architecture manifests and story files to produce clear sprint-level completion criteria and targeted testing requirements.
imclabGenerate structured QA test plans from sprint stories and GDD acceptance criteria.
Euraika-LabsGenerate structured QA test plans from project story files and artifacts.
wayne930242Classify knowledge tasks and delegate them to appropriate Claude Code skills via the Skill tool.
KotuhanGenerate test case and regression checklist templates for QA planning.
