Launch specialist
Maestro
Coordinate the work.
Coordinates specialist work, checks its verification, and decides when independent testing is useful.
Specialist coordination
AI Agents for Game Development
EngineForge Crew brings specialist roles to different parts of game-development work. Maestro coordinates the task with serial specialist tool calls when useful, and the developer stays in control of the result.
Meet the Crew
Specialist roles for different parts of the work.
The launch Crew is the starting roster, not a fixed limit. The right role depends on the task; all five do not participate by default.
Launch specialist
Prototyper
Get the idea playable.
Builds the first playable slice.
Launch specialist
Juicer
Make the interaction feel alive.
Improves feel, feedback, and presentation.
Launch specialist
Systems Smith
Build it to last.
Builds durable systems, UI, and persistence.
Launch specialist
Playtester
Verify what happens in the game.
Runs the game and verifies behavior from evidence.
One task, the right specialist tools
Add a dash ability to an existing player controller.
One illustrative workflow shows Maestro using serial specialist tool calls without turning Crew into a mandatory pipeline.
Illustrative request
“Add a dash ability to the existing player controller.”
Request
Developer
Defines the desired dash behavior.
Maestro
Coordinates the dash work.
Bounded concern
Build the dash ability and report specialist-owned verification of the behavior.
Serial tool call →← Result
Specialist work
Juicer
Result returns. Maestro reviews specialist-owned verification and sanity checks.
Optional
Runtime verification
Playtester
Runs conditional independent testing when a separate check is useful.
Final destination
Developer review
Inspect the changes and relevant evidence.
This example is illustrative. Maestro does not call every specialist, specialist tool calls are serial, and not every request delegates or re-verifies. Independent testing is conditional when the task warrants a separate check.
Maestro coordination
Specialist work stays reviewable.
Maestro coordinates serial specialist tool calls, reviews specialist-owned verification, and records sanity checks before relying on a result.
Read Maestro coordination details →Coordination
Maestro leads
One relevant specialist tool at a time.
Maestro makes serial specialist tool calls only when they help the task, so work and evidence stay easy to inspect.
Verification
Specialist-owned
Evidence receives a sanity check.
The specialist reports its verification. Maestro reviews sanity checks and uses conditional independent testing only when a separate check is useful.
Plan before you act
Understand first. Act with boundaries.
Read-only understanding
Inspect the project, reason about the request, and decompose the work without changing files.
Action-enabled work
Let the selected role use appropriate action capabilities within applicable approval boundaries.
Review the work
Crew coordination stays visible.
The work does not disappear into an invisible autonomous process. The developer can inspect what changed, what each specialist returned, and what evidence supports the result.
Specialist results
See what each specialist returned to Maestro.
Approvals
Keep applicable action boundaries and decisions visible.
Changes and diffs
Inspect the project changes produced during the work.
Code checkpoints
Review captured code states before deciding what stays.
Specialist verification
Review the evidence each specialist used to check its work.
Maestro sanity checks
Inspect checks, blockers, and any follow-up testing decision.
Built to grow
Five specialists are the beginning of the Crew.
The launch roster is not the permanent product limit. EngineForge’s extensible Crew can support additional specialists and capabilities over time without turning every task into an all-agent workflow.
Choose the next step
Bring the right specialist into the work.
Explore the Crew in detail or download EngineForge to see the workflow in the platform.
Maestro coordination →