> For the complete documentation index, see [llms.txt](https://gameterminal.gitbook.io/gameterminal-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gameterminal.gitbook.io/gameterminal-docs/core-infrastructure/overview/agent-development-framework.md). # Agent Development Framework The Agent Development Framework is the autonomous execution layer of GT Protocol, responsible for transforming structured development plans into complete, playable gaming experiences. Rather than relying on a single AI model to generate an entire game, GT Protocol distributes responsibilities across a network of specialised AI agents that collaborate throughout the development lifecycle. Each agent is designed to perform a dedicated role, whether generating gameplay mechanics, writing production-ready code, designing environments, creating characters, producing visual assets, synthesising audio, or validating quality. By decomposing complex development workflows into specialised tasks, the framework enables parallel execution, greater consistency, and significantly higher output quality. Every agent operates within a shared execution environment managed by the AI Orchestration Engine. This shared context allows agents to continuously exchange information, understand project dependencies, and build upon each other's work without losing consistency across gameplay systems, art direction, world design, or user experience. Unlike traditional AI workflows that terminate after producing an initial output, the Agent Development Framework operates as an adaptive development pipeline. Agents continuously evaluate intermediate results, request additional context when required, and collaborate with specialised evaluation agents to refine generated content before it reaches the creator. The framework is designed to scale dynamically with project complexity. Simple prototypes may activate only a small subset of agents, while larger productions automatically expand into a collaborative network capable of managing every aspect of game development simultaneously. ### Agent Categories GT Protocol organises autonomous agents into specialised production domains. #### Design Agents Responsible for gameplay mechanics, progression systems, balancing, level design, player experience, and game economy. #### Engineering Agents Generate production-ready source code, gameplay logic, system architecture, debugging, optimisation, and technical implementation. #### Creative Agents Produce characters, environments, visual assets, animations, textures, audio, voice synthesis, and user interface components. #### Evaluation Agents Continuously analyse functionality, gameplay quality, performance, visual consistency, accessibility, and overall production readiness before approving each generation stage. Together, these specialised agents function as a collaborative AI development team capable of autonomously producing complete gaming experiences while maintaining consistency across every creative and technical discipline. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://gameterminal.gitbook.io/gameterminal-docs/core-infrastructure/overview/agent-development-framework.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.