gameplay-implementation-review

To verify design intent during gameplay code review, perform a structured three-pass workflow validating handoff acceptance criteria, mechanic soul preservation, and code quality against concrete pull request changes.

The best way to review gameplay PRs for scope drift is a three-pass workflow checking design intent survival, critical issues like frame budget violations, and informational findings to flag misalignments early.

Detect frame budget violations and input latency by executing Pass 1 of the gameplay review workflow, which identifies critical performance issues, memory risks, and serialization problems in code changes.

Yes, you can apply gameplay implementation review across different game engines and team workflows, validating code changes and design intent without requiring specific dependencies or component setups.

Generate a structured artifact report for game QA by running the review workflow against a pull request, outputting the implementation review findings to the shared project directory for downstream consumption.

Use the adversarial pass for gameplay code review when evaluating large diffs, stress-testing the implementation to surface deeper scope drift and design-value alignment issues not caught by standard passes.