qa-plan

Generate a structured QA plan by parsing sprint, feature, and story references alongside GDD inputs. The skill classifies each story by test type and outputs a complete test matrix, automated tests, manual checks, and smoke test scope to a markdown file.

Classify stories by test type by evaluating acceptance criteria and any Type field. The skill categorizes each story into Logic, Integration, Visual, UI, Config, or Data test types to build a comprehensive test matrix for the sprint.

Yes, you can define Definition of Done and playtest requirements upfront. The generated QA plan document includes DoD criteria for sprint completion and outlines specific playtest requirements alongside manual checks and smoke tests.

No specific dependencies are required to parse GDD inputs. The skill directly reads sprint, feature, and story scope and loads related GDDs to determine the testing scope without needing external components.

Create a QA plan before starting a sprint or major feature to ensure test coverage is defined upfront. This prevents rushed or inconsistent QA planning by producing a structured document detailing automated and manual testing scope.

The sprint QA plan outputs to a markdown file located at production/qa/qa-plan-[sprint-slug]-[date].md. This file contains the full test matrix, smoke test scope, and Definition of Done criteria.