analyst
01Agent Claude Code
Analyzes listed user-provided art/audio asset candidates and writes assets/manifest.json. Read-only on game code.
Autonomous text-to-game pipeline for Godot, powered by Claude Code,Codex,Opencode
This repository also configures its own agents. See what GodotMaker tells them →
Agent Claude Code
Analyzes listed user-provided art/audio asset candidates and writes assets/manifest.json. Read-only on game code.
Agent Claude Code
Produces one assigned visual asset production unit for the asset stage. Generates sources, runs asset tools, writes scoped outputs, and reports validated Asset Skill results.
Agent Claude Code
Decomposes a confirmed GDD + ROADMAP into the current tag's artifact set — PLAN.md, STRUCTURE.md, SCENES.md, DESIGN.md, TOC.md, plus appends new rows to the cross-tag ASSETS.md (and optionally project.godot tweaks). Owns sub-stage 1c of /gm-gdd. Returns only a short summary so the lead's context stays lean.
Agent Claude Code
Independent GDD reviewer. Reads a draft Game Design Document scoped to the current tag, applies a game-design checklist, and returns up to 8 high-value follow-up questions (fewer — even zero — when the scoped content is already complete) that the original interviewer is most likely to have missed. Read-only — MUST NOT…
Agent Claude Code
Post-implementation code reviewer for Godot game projects. Reads implemented code, decides which domain-specific reviewer skills apply, runs their checklists, and reports issues found. MUST NOT modify project files.
Agent Claude Code
Verification specialist for testing and validating artifacts. Runs ALL checks, reports pass/fail. MUST NOT modify project files. Lead agent will spot-check results.
Agent Claude Code
Implements bounded units of work for Godot game projects. Receives a structured brief, implements code + tests, and reports execution results and failure evidence.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: