godot-tdd_skill

Overview

This skill coordinates a Test-Driven Development (TDD) workflow for Godot projects, acting as the central controller that sequences design, test, implementation, verification, and final test phases. It orchestrates the godot-design, godot-test, godot-dev, and godot-verify sub-skills to enforce a repeatable development loop and quality gates. The goal is to keep changes small, tested, and reviewable until features are complete.

How this skill works

The skill accepts actions like start and next_phase and advances a feature through phases: design (interface/spec generation), test (write failing tests), implement (minimal code to pass tests), verify (lint/format/error checks), and run_test (full-suite verification). It delegates specific tasks to sub-skills: godot-design for interface specs, godot-test for GUT tests and runs, godot-dev for implementation, and godot-verify for lint/format/error checks. Progress states are tracked and a loop is enforced until the feature reaches completed.

When to use it

• Building Godot game features following strict TDD practices
• Enforcing interface-first development and traceable design changes
• Ensuring every change passes lint/format and automated tests before merge
• Coordinating multi-role teams (designers, devs, testers) with a single workflow
• Automating repetitive TDD cycles with minimal human intervention

Best practices

• Start each feature by defining interfaces and observable state query methods before implementation
• Write focused, failing tests (red) that express exact expected behavior
• Implement the smallest change to make tests pass (green), then refactor while keeping tests green
• Run godot-verify (gdlint, gdformat, error parsing) after implementation and before final test runs
• Never change public interfaces directly in code — update design docs and re-run design review

Example use cases

• Create a Player damage system: design public methods and signals, write GUT tests, implement minimal logic, run verify and full tests
• Add a new gameplay mechanic where interface changes demand design approval before implementation
• Automate CI step: on feature branch start, run TDD loop until all tests and lint pass, then mark completed
• Onboarding: enforce consistent test naming, design docs, and file structure for new contributors