A team uses two agents to generate code for different modules of the same service. When the modules are integrated, developers find they use completely different naming conventions, error handling patterns, and code structure — one uses camelCase with try/catch blocks, the other uses snake_case with result tuples. No conflicts occur during generation. What coordination element is missing?
Select an answer to reveal the explanation.
Short Explanation
Two agents building code without a shared style guide are like contractors using different building codes. You need the same coding standards in both prompts and a consistency check before integration.
Full Explanation
Stylistic and structural consistency across multi-agent code generation requires explicit coordination of standards. When two agents each generate code independently using their own default style, the outputs will reflect each model's individual patterns, training distributions, and prompt phrasing, producing internally consistent but mutually inconsistent codebases. The two coordination mechanisms that address this are shared standards injection and a cross-agent consistency gate. Shared standards injection means providing both agents with the same coding standards document as part of their system prompt, including naming conventions, error handling patterns, file structure expectations, and type annotation requirements, so their generation is aligned from the start. A cross-agent consistency gate means that after both agents complete generation, you run a consistency check before integration, such as automated linting against the shared standards or an LLM judge comparing the two outputs for stylistic alignment. The suggestion to merge the two agents into a single agent would solve the consistency problem but eliminates the parallelism, specialization, and modularity of the multi-agent design; it is a valid choice for small scopes but is not the right answer for maintaining the multi-agent architecture. The suggestion that the orchestrator should have prevented the two agents from generating code at the same time imposes serial execution, which eliminates one potential source of inconsistency, concurrent divergence, but does not actually align the agents' styles. The second agent would still generate in its own style unless given the first agent's output as a style reference, which is a different coordination approach, style-from-example, rather than serial execution itself. The suggestion that one agent's output should have been discarded and the other's used exclusively wastes the work of the discarded agent and eliminates the productivity benefit of multi-agent generation. Shared coding standards with consistency validation is the scalable solution for multi-agent code coherence.