Tools for implementation-planning

Planning which automated test cases to write

Test command:

mise exec -- godot --headless -s addons/gut/gut_cmdln.gd -gdir=res://tests/unit -gexit

Uses GUT v9.7.1 — see docs/tools/test-writer.md for the same command and its caveats. Plan automated test cases around what this can run headlessly; anything it can't reach (editor/game state) is a candidate for a manual test driven through godot-ai instead.

Plan test cases that can fail. When writing an expected value into the plan, pick one where the correct answer, the plausible wrong answer, and the not-yet-implemented answer are three different values — otherwise the test written from that row cannot tell them apart, and the human at the freeze gate approves a specification that pins nothing. The same applies to a row asserting a rejection: say which mechanism must cause it, since anything else that rejects produces the same observable outcome.

Deciding what a manual test should verify

Consider godot-ai when scoping a manual-test step — it can drive/inspect the live editor and running game, so a step can be written against what it can actually check rather than a vague human judgement call. That file has the criterion for when it applies.

Record automated/manual per acceptance criterion with the reason, so the routing is reviewable rather than inherited.