Use paired agents to plan and code a Godot game

One agent handles the game plan and task list while another writes GDScript, checks the build, and prepares commits for approval.

Done with Claude CoworkClaude Codeยท Intermediate

What they did
A developer copied the Claude4Godot folder into their Godot project and let Claude Cowork create a set of Markdown files for the design doc, task queue, system map, and personas. Cowork then held design sessions, updated the design document, and sorted the work into tasks. Claude Code took the next available task, wrote the script, ran Godot in headless mode to verify it, and prepared a git commit.
How it went
The workflow was described as a process, not as a finished project. No game examples, measurements, or other results were given. The developer reviewed the design choices and approved each commit and push.
Tips
Keep the human in charge of design decisions and approvals. Only Claude Code was set up to run Godot and git, while Cowork only listed changed files and generated a commit message to paste in.

Try it yourself with Claude Code

I want to build a small Godot game at [project path] about [game idea]. Start by creating a short design document, a task list ordered by priority, a system map, and player personas in Markdown. Then, for each task, choose the next ready item, write the GDScript, run a headless Godot check, and prepare a git commit message. Before any commit, push, payment, deletion, or submission, stop and ask me to approve it. After [number] tasks, tell me what should be playtested next.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on github.com โ†—

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.