Generate structured QA test plans from sprint story files and GDDs.
npx skills add https://github.com/easonlao/jiazi-game --skill qa-plan-easonlao
Please help me install this Agent Skill. Skill: qa-plan Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/qa-plan Command: npx skills add https://github.com/easonlao/jiazi-game --skill qa-plan-easonlao
It prevents late surprises by turning sprint or feature scope into a clear, structured QA plan that developers, QA, and designers can follow before implementation starts.
Ask the qa-plan skill with the argument sprint to generate a complete QA test plan for the current sprint and save it under production/qa/.
High-intent search queries and answers about installing and using this skill.
To generate a QA test plan, parse in-scope story files and referenced GDDs to extract acceptance criteria, then classify stories into test types and output a structured markdown plan. This translates sprint scope into unit, integration, manual, smoke, and playtest verification steps.
Translating acceptance criteria into smoke testing and playtest sign-off steps requires classifying each story into Logic, Visual, or Config types. This classification maps criteria directly to specific automated test file paths and manual verification procedures.
Yes, qa-plan works with GDD formula references by reading them during scope parsing. It includes guardrails in the test plan to flag any missing GDD formula references, ensuring accurate verification step generation for logic and integration stories.
Classify sprint stories into Logic, Integration, Visual, UI, or Config/Data types by analyzing their acceptance criteria and any provided Type field. This story-type classification determines the appropriate automation coverage and manual verification paths needed.
Yes, you can generate an individual story QA test plan by providing a specific story path instead of a sprint or epic scope. The plan reads that single story file and its referenced GDDs to output tailored verification steps.
Generating QA plans for projects without defined acceptance criteria limits the ability to classify stories into test types and map verification steps. The process relies on parsing these criteria to produce unit, integration, and smoke test coverage accurately.
emcconnellGenerate structured QA test plans from story files and GDDs.
FrancisVargaGenerate structured QA test plans from story files and GDD acceptance criteria.
slgoodrichGenerate user story templates with acceptance criteria and INVEST validation.
johnatas-henriqueGenerate structured QA test plans for game development sprints.
