qa-plan

You can generate a sprint QA test plan by reading referenced story inputs and their cited GDD or ADR requirements, categorizing stories into Logic, Integration, Visual/Feel, UI, or Config/Data, and mapping them to automated and manual verification work.

Story classification in pre-sprint QA planning assigns each story a primary QA type, such as Logic, Integration, Visual/Feel, UI, or Config/Data, based on acceptance criteria and existing Type fields to allocate automated and manual tests.

Yes, the QA planning process handles missing referenced files without failing, allowing it to parse available acceptance criteria and GDD formulas to produce a structured test plan even with incomplete documentation.

Map acceptance criteria to automated tests and manual checklists by pulling relevant GDD Acceptance Criteria and Formulas, scanning architecture guardrails, and deriving verification checks based on what must be true for the feature.

The best way to define a Definition of Done gate is to generate an execution-ready QA plan that includes smoke test scope, manual QA checklists, playtest sign-off requirements, and automated test file paths derived from sprint requirements.

Yes, you can build a QA plan for a single feature, full epic, or individual story by resolving the referenced story inputs, parsing their acceptance criteria, and writing the output plan to the production QA directory.