team-audio

Managing a game audio pipeline requires coordinating audio directors, sound designers, and programmers. This Skill orchestrates that team by spawning subagents for each role, reading design docs, and outputting a structured audio design document for the target feature.

You generate an audio design document by providing game feature context. The Skill reads existing design docs and the sound bible, then orchestrates a multi-role team workflow to output a versioned design document at design/gdd/audio-[feature].md.

Yes, you can coordinate sound design and implementation for combat encounters. The Skill applies to combat, menus, environments, and boss encounters, bridging the gap between sonic identity direction and technical gameplay integration.

Aligning audio assets with game design requires shared context. This Skill reads files from design/gdd and assets/audio/, grounding all audio team decisions and deliverables in the existing project design document structure.

A sound bible is not strictly required but is highly supported. The Skill actively reads design/gdd/sound-bible.md if present to ground decisions, while also gathering necessary context from general design docs and existing asset lists.

Team orchestration handles approvals through a structured decision workflow. The Skill uses an AskUserQuestion mechanism at each step of the pipeline, ensuring role-based alignment and versioned outputs before finalizing the audio design document.