Convert GDDs and stories into structured QA plans with test coverage.
npx skills add https://github.com/rakhnianskii9/God-Godot --skill qa-plan-rakhnianskii9
Please help me install this Agent Skill. Skill: qa-plan Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/qa-plan Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill qa-plan-rakhnianskii9
QA teams often struggle to design comprehensive test plans that cover all acceptance criteria across sprints, features, and user stories. This skill automates the creation of a complete QA plan from GDDs and story files, ensuring consistent coverage and faster sprint readiness.
Provide a scope (sprint, feature, or story) and run the skill to generate a complete QA plan.
High-intent search queries and answers about installing and using this skill.
Generate a QA test plan by parsing sprint plans, features, or individual stories, resolving GDD references, classifying test types, and outputting a structured document with automated tests, manual checks, and sign-off criteria.
Automate sprint QA planning by reading in-scope story files and their GDD references to map acceptance criteria to specific automated tests, manual verification tasks, and playtest requirements, producing a comprehensive coverage document.
Yes, you can create a QA plan for an individual story, specific feature, or full sprint scope. The process reads the targeted story files and resolves missing GDD references to generate testable requirements for that exact scope.
Map game design formulas to testable edge cases by respecting GDD references within story files to derive specific test requirements, classifying them into Logic, Integration, Visual, UI, or Config/Data categories for manual and automated testing.
When GDD references are missing, the test plan generation flags information gaps explicitly. It resolves available references to derive testable requirements but highlights missing data to ensure QA coverage remains accurate and transparent.
QA plan automation categorizes stories into Logic, Integration, Visual, UI, and Config/Data test types. It then generates a formal document detailing automated tests, manual verification, smoke test scope, and specific playtest readiness requirements.
sethdfordGenerate sprint plans and risk assessments from team capacity and velocity.
storyblokAnalyze code changes to generate a structured QA review plan.
Euraika-LabsOrchestrates end-to-end sprint QA with smoke checks, test plans, and sign-off reports.
imclabGenerate structured QA test plans from sprint stories and GDD acceptance criteria.
