Build Godot games with paired design and coding agents
Make the game you designed, with AI doing the building and you staying the director. Task: The author implemented a workflow for Godot 4 projects where the human acts as director, deciding design, balance, and priorities, while AI agents handle building, testing, and record-keeping. The system uses Claude Code (tested) or other assistants reading AGENTS.md to execute tasks in fresh contexts, ensuring design decisions are presented as options for human approval before code changes are committed. Human involvement is mandatory for approving summaries, commits, and resolving open questions, preventing AI from guessing mechanics or leaving 'done' as merely 'compiled'.; tools: Claude Cowork, Claude Code. Human role: The original post does not say how a person stayed involved.; limitations: Requires Godot 4.5+, git, and bash; gitleaks is recommended for secret scanning. Only Claude Code is explicitly tested; other assistants are unverified. The workflow relies on human approval for every commit and design decision, which may slow down rapid prototyping if not managed carefully. Privacy is maintained as the tool runs locally and sends no data externally..
Tools
Published on Agent Work Atlas:
Overview
Make the game you designed, with AI doing the building and you staying the director.
Workflow
The author implemented a workflow for Godot 4 projects where the human acts as director, deciding design, balance, and priorities, while AI agents handle building, testing, and record-keeping. The system uses Claude Code (tested) or other assistants reading AGENTS.md to execute tasks in fresh contexts, ensuring design decisions are presented as options for human approval before code changes are committed. Human involvement is mandatory for approving summaries, commits, and resolving open questions, preventing AI from guessing mechanics or leaving 'done' as merely 'compiled'.
Reported result
The source does not report specific measured outcomes, success rates, or performance metrics for this workflow. It describes the intended behavior: preventing design drift, ensuring 'done' means tests pass, and maintaining context across sessions via plain files. No evidence of actual project completion times or bug reduction rates is provided in the text.
Human role
The original post does not say how a person stayed involved.
Limitations
Requires Godot 4.5+, git, and bash; gitleaks is recommended for secret scanning. Only Claude Code is explicitly tested; other assistants are unverified. The workflow relies on human approval for every commit and design decision, which may slow down rapid prototyping if not managed carefully. Privacy is maintained as the tool runs locally and sends no data externally.
Try it
I want to set up the Godot Director workflow for my game project. My project is located at [replaceable: project_path], uses Godot 4.5+, and has a git repository with no uncommitted changes. I have written my Game Design Document at [replaceable: gdd_path]. Please install Godot Director using the Claude Code plugin method: run '/plugin marketplace add Freakling/Godot-Director' and then '/plugin install godot-director@godot-director'. After installation, open a new session in my project folder and run '/godot-director:godot-director' to start onboarding. During onboarding, read my GDD and ask me about any open questions. Do not make any design decisions or write any code without my explicit approval. First, perform a dry run: propose one small task from my GDD, show me the plan and the files it will touch, and wait for my confirmation before executing. If I approve, execute the task, run the check (bash tools/check.sh), and show me the results before committing. If the check fails, stop and report the error. Do not push to any remote repository. Confirm you understand these steps before proceeding.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.