game-build

You can build Godot 4.x features using TDD by mapping requirements to design techniques and generating RED-GREEN-REFACTOR cycles with automated test scaffolding. The process creates a coherent build plan with integration tests and playtest readiness directly from your feature inputs.

Mapping Godot 4.x feature requirements involves categorizing needs into TDD, Implementation First, or Implementation Only techniques. This generates corresponding tests and scaffolding, ensuring a structured build cycle from initial planning through regression gates and playtests.

To start a technique-mapped build cycle for Godot 4.x, define your requirements using a feature.json input containing requirements, buildSequence, and files. Running the build process consumes this input to update backlog and context while producing a structured progress report and git baseline.

Yes, feature.json is required to generate GDScript test scaffolding for Godot 4.x. The file provides the necessary requirements, buildSequence, and files data that the build cycle uses to map techniques and create the corresponding test plans and resource setups.

Yes, implementation-first visual and scene setup is supported without writing tests first in Godot. The technique mapping categorizes features into TDD, Implementation First, or Implementation Only, allowing direct resource creation guided by your feature.json when tests are not prioritized.

Integration playtests are limited to Godot 4.x projects and depend on completing the full build pipeline including define, plan, build, test, debug, and refactor stages. Regression gates must be passed before playtest planning and execution can proceed.