team-audio

Game audio design and technical implementation can be coordinated by orchestrating subagents for audio direction, sound design, engine validation, and gameplay programming. This pipeline reads design documents and audio assets to output a consolidated audio design document with specific implementation tasks.

Game audio accessibility requirements are met by identifying critical gameplay audio events and specifying visual fallbacks and caption requirements. The pipeline surfaces accessibility gaps before implementation, validating that all necessary audio cues have compliant alternatives.

Audio middleware integration and memory budgets are validated by reading design documents and audio asset lists to check engine-specific patterns. The pipeline proposes memory and streaming budgets while delegating file writes to subagents for technical validation.

Team audio orchestration can be used for feature-level scenarios including biomes, boss encounters, combat, and main menus. It coordinates outputs from audio directors, sound designers, technical artists, engine specialists, and gameplay programmers to produce aligned audio deliverables.

Deliverables from an orchestrated game audio pipeline include SFX specifications, audio event lists, middleware routing details, and implementation tasks. These are compiled and saved as a consolidated audio design document at design/gdd/audio-[feature].md.

Automating audio director and sound designer collaboration is best handled by spawning coordinated subagents within a structured pipeline. This approach aligns technical artists, engine specialists, and gameplay programmers to produce comprehensive audio design without manual coordination overhead.