team-audio

Orchestrates four audio subagents to produce a complete game audio design document.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill team-audio-onemanking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-audio
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/team-audio
Command: npx skills add https://github.com/onemanking/the-operator --skill team-audio-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing game audio requires coordinating direction, sound design, technical implementation, and code integration, which is difficult to manage as a single workflow. This Skill orchestrates a four-agent audio team through a structured pipeline with user approval at each step. ## Core Features & Use Cases - Sequential Team Orchestration: Spawns audio-director, sound-designer, technical-artist, and gameplay-programmer subagents in order, each building on prior outputs. - User Decision Gates: Presents each agent's proposals via AskUserQuestion so the user approves direction before the next step begins. - Compiled Design Document: Merges all team outputs into a single audio design doc saved to design/gdd/audio-[feature].md. - Use Case: Ask for audio design for a boss encounter, and the pipeline defines sonic identity, SFX specifications, bus structure and memory budgets, then wires audio events to gameplay triggers. ## Quick Start Invoke the team-audio skill with a feature name like "boss encounter" to run the full audio design pipeline.

Frequently Asked Questions about team-audio

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design game audio for a specific feature or area?

Invoke the skill with the target feature name, such as combat or main menu. It runs four subagents in sequence covering audio direction, sound design, technical implementation, and code integration, then compiles a design document.

What agents are involved in the audio design pipeline?

The pipeline uses four subagents: audio-director for sonic identity, sound-designer for SFX specifications, technical-artist for middleware and bus structure, and gameplay-programmer for audio manager code and gameplay triggers.

Can I approve or reject proposals between pipeline steps?

Yes. At each step transition the skill presents the subagent's proposals through AskUserQuestion as selectable options. The user must approve before the pipeline moves to the next step.

Where is the final audio design document saved?

The compiled document combining all team outputs is saved to design/gdd/audio-[feature].md, where [feature] is the argument passed to the skill. A summary with event counts and open questions is also output.

What inputs does the audio pipeline need before starting?

It reads relevant design docs in design/gdd/, the sound bible at design/gdd/sound-bible.md if present, and existing audio asset lists in assets/audio/. Providing a clear feature argument improves results.