team-audio

An audio pipeline workflow coordinates audio direction, sound design specs, middleware integration, and gameplay triggers to produce a unified sonic identity. It delegates tasks across specialized roles like audio director and gameplay programmer to output complete audio event specifications.

Adaptive music direction maps gameplay triggers to dynamic audio states, ensuring the sonic identity responds to player actions. The system orchestrates these gameplay integration events to specific audio behaviors, preventing critical state changes from being communicated by audio alone.

Yes, the audio orchestration workflow supports a solo review mode designed for individual developers. This mode controls the delegation of subagent tasks, allowing a single developer to efficiently generate complete SFX and audio event specifications without a full audio team.

The best way to document audio accessibility is to generate an accessibility-first audio spec ensuring gameplay state is never communicated by audio alone. This specification is written directly into the audio design document alongside middleware and bus plans.

Yes, the generated audio design document includes complete middleware integration plans and engine-specific audio wiring. It coordinates the primary engine specialist and technical artist to map out the audio bus structure and asset workflows for the specified feature.

The audio design output uses a markdown file format, specifically written to design/audio/audio-[feature].md. This document structure consolidates the audio direction, SFX specifications, and gameplay integration plans into a single reviewable file.