team-audio

Game audio pipeline coordination structures audio direction, sound design, technical implementation, and gameplay programming into specialized subagents. This orchestrates an end-to-end pipeline ensuring collaborative delivery for features like combat or menus.

Generating an audio design document requires orchestrating specialized subagents to process feature requirements. This consolidated pipeline outputs a design document at design/gdd/audio-[feature].md, complete with milestones, asset estimates, and outstanding questions.

Adaptive music system integration is handled by coordinating technical artists and gameplay programmers within the audio pipeline. It defines event specs and middleware integration, ensuring the dynamic music adapts to gameplay states across features.

Yes, the audio pipeline applies to specific game encounters like boss fights or forest environments. Providing the feature name assembles the full audio team pipeline, directing subagents to define audio direction and create event specs for that context.

No external dependencies or components are required to start the game audio team pipeline. You simply provide the target feature name to begin assembling the subagents for audio direction, sound design, and technical implementation.

An end-to-end game audio workflow outputs a consolidated audio design document alongside a project summary. The summary includes milestones, asset estimates, and outstanding questions, ensuring all technical and design requirements are captured.