qa-plan

Sprint QA test plan generation handles missing story files and missing GDD sections by classifying them as reportable gaps rather than stopping execution. It reads available story files, extracts Acceptance Criteria, Formulas, and Edge Cases, and produces a deterministic test plan covering those gaps.

Mapping story acceptance criteria to testing activities involves classifying each story into Logic, Integration, Visual/Feel, UI, or Config/Data test types. The QA plan then extracts referenced GDD requirements to explicitly define automated test requirements and manual verification steps.

Story classification by test type assigns Logic, Integration, Visual/Feel, UI, or Config/Data categories based on declared Type headers. When Type headers are absent, the system infers the appropriate test type from indicators found within the acceptance criteria.

QA test plan generation requires YAML frontmatter-defined configuration for setup and executes with zero dependencies. Scope resolution occurs via argument parsing or interactive prompting, reading story files and referenced GDDs to build the structured output.

QA test plan generation supports sprint, feature, epic-wide, or single story path scope inputs via interactive prompts or arguments. It resolves the requested scope, reads the corresponding story files, and maps the requirements to smoke test scope and playtest sign-off expectations.

Forbidden-pattern scanning during pre-implementation QA planning identifies specified patterns within story files and referenced GDDs. Rather than stopping execution, it incorporates these findings into the deterministic output document alongside smoke and playtest requirements.