qa-plan

You can automate sprint test plan generation by parsing project story files, GDDs, and artifacts to classify story types and output a markdown document containing test summaries, automated test specs, manual checklists, and smoke test scope.

Story classification in QA test planning categorizes project stories into Logic, Integration, Visual/Feel, UI, or Config/Data types based on acceptance criteria to outline required automated and manual tests.

You can create manual checklists and smoke test scopes by parsing GDDs and project artifacts to detect scope and generate a structured markdown document containing manual checklists, smoke test lists, and playtest sign-off requirements.

Yes, you can automate test plan creation for features by parsing project artifacts to determine scope and produce a comprehensive QA document covering automated test specifications, manual checks, and playtest requirements.

To generate structured QA documents for playtest sign-off, you need project story files, GDDs, and related artifacts available for parsing to determine scope and produce test summaries with sign-off requirements.

Yes, qa-plan works with game design documents by parsing GDDs alongside story files to classify story types and outline required automated and manual tests within the generated test plan.