regression-suite

To verify bug fixes with regression tests, run an update mode that scans closed bugs in `production/qa/bugs/*.md` and checks if matching regression tests exist. This fixed-bug regression verification prevents repeat failures by ensuring every resolved issue has corresponding test coverage before passing release gates.

A regression suite manifest is a curated single source of truth maintained in `tests/regression-suite.md` that indexes specific tests which must stay passing. It prevents game regressions by detecting coverage drift when new systems have insufficient regression coverage, flagging likely staleness before release gates.

You audit test inventory for missing regression coverage by scanning the `tests/` directory and parsing GDD systems from `design/gdd/systems-index.md`. The audit mode generates coverage and drift reports that label critical path coverage as COVERED, PARTIAL, MISSING, or EXEMPT to identify gaps.

Regression testing for game QA works without external dependencies, relying solely on reading and writing `tests/regression-suite.md`, scanning test inventory under `tests/`, parsing GDD systems, and analyzing closed bugs. It requires no additional components to maintain manifests and audit coverage drift.

You should detect coverage drift when new systems or stories are added to your game. The Skill flags likely staleness by checking if new features have insufficient regression coverage mapped to GDD critical paths, preventing new features from drifting coverage away from what the game depends on before release gates.