OpenParable
Skip to content
← Back to skills

Team Audio

Productivity
team-audio

Team Audio is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/orchestration/team-audio/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/team-audio, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

When this skill is invoked:

  1. Read the argument for the target feature or area (e.g., combat, main menu, forest biome, boss encounter).

  2. Gather context:

    • Read relevant design docs in design/gdd/ for the feature
    • Read the sound bible at design/gdd/sound-bible.md if it exists
    • Read existing audio asset lists in assets/audio/
    • Read any existing sound design docs for this area

How to Delegate

Use the Task tool to spawn each team member as a subagent:

  • subagent_type: audio-director — Sonic identity, emotional tone, audio palette
  • subagent_type: sound-designer — SFX specifications, audio events, mixing groups
  • subagent_type: technical-artist — Audio middleware, bus structure, memory budgets
  • subagent_type: gameplay-programmer — Audio manager, gameplay triggers, adaptive music

Always provide full context in each agent's prompt (feature description, existing audio assets, design doc references).

  1. Orchestrate the audio team in sequence:

Step 1: Audio Direction (audio-director)

Spawn the audio-director agent to:

  • Define the sonic identity for this feature/area
  • Specify the emotional tone and audio palette
  • Set music direction (adaptive layers, stems, transitions)
  • Define audio priorities and mix targets
  • Establish any adaptive audio rules (combat intensity, exploration, tension)

Step 2: Sound Design (sound-designer)

Spawn the sound-designer agent to:

  • Create detailed SFX specifications for every audio event
  • Define sound categories (ambient, UI, gameplay, music, dialogue)
  • Specify per-sound parameters (volume range, pitch variation, attenuation)
  • Plan audio event list with trigger conditions
  • Define mixing groups and ducking rules

Step 3: Technical Implementation (technical-artist)

Spawn the technical-artist agent to:

  • Design the audio middleware integration (Wwise/FMOD/native)
  • Define audio bus structure and routing
  • Specify memory budgets for audio assets per platform
  • Plan streaming vs preloaded asset strategy
  • Design any audio-reactive visual effects

Step 4: Code Integration (gameplay-programmer)

Spawn the gameplay-programmer agent to:

  • Implement audio manager system or review existing
  • Wire up audio events to gameplay triggers
  • Implement adaptive music system (if specified)
  • Set up audio occlusion/reverb zones
  • Write unit tests for audio event triggers
  1. Compile the audio design document combining all team outputs.

  2. Save to design/gdd/audio-[feature].md.

  3. Output a summary with: audio event count, estimated asset count, implementation tasks, and any open questions between team members.