Files
codex-game-studio/.agents/skills/cgs-team-audio/SKILL.md
T
7e8846a7fb feat: add deterministic model tier routing (#14)
* feat: add deterministic model tier routing

Define Sol, Terra, and Luna policies with fixed fallbacks, explicit surface assignments, runtime precedence, and Luna escalation. Validate generated metadata and expose tier overrides across role, task, and orchestration commands.

* fix: infer model tiers from surface models

* fix: rebalance prompt model routing

* fix: decouple prompt effort routing

---------

Co-authored-by: MerlinH <merlinh221@gmail.com>
2026-07-10 18:49:20 +10:00

2.5 KiB

name, description, model, model_reasoning_effort, argument-hint, primary-agent, tool-policy, isolation, source-reference, source-hash, user-invocable
name description model model_reasoning_effort argument-hint primary-agent tool-policy isolation source-reference source-hash user-invocable
cgs-team-audio Use for team audio tasks that coordinate audio design, implementation, asset readiness, mix targets, and QA for audio work; produce verification evidence, changed or proposed files, and handoff boundaries. gpt-5.6-terra low Describe the team-audio objective, target files/assets, constraints, and verification evidence. game-designer read/edit/shell/tests/git as needed within the repository write policy repository-root; no init-time generated prompt bodies .claude/skills/team-audio/SKILL.md 6dd03358962dbef74b6c67e7d34383e0721571a534b75f1ba562f39e92287416 true

Codex Game Studio Team Audio

Use this skill for team audio work in Template Game.

Objective

Coordinate audio design, implementation, asset readiness, mix targets, and QA for audio work.

Inputs

  • AGENTS.md
  • .codex/studio.json
  • task-relevant files named by the user or task record
  • design/gdd.md
  • production/timeline.md
  • task-relevant team files

Arguments

  • Objective or user request.
  • Target files, scenes, assets, or docs.
  • Constraints, deadlines, acceptance criteria, and verification command when known.

Procedure

  1. Clarify the requested coordinate audio design, implementation, asset readiness, mix targets, and qa for audio work. and identify the current project stage.
  2. Collect evidence for Audio Goal, Asset Need, Mix Target.
  3. Coordinate handoffs between disciplines and name each owner, artifact, and validation need.
  4. Produce the requested artifact or review with clear file paths and verification evidence.

Write Targets

  • production/
  • design/

Output Contract

  • Summary
  • Audio Goal
  • Asset Need
  • Mix Target
  • QA Note
  • Risks
  • Changed files or proposed files
  • Verification evidence
  • Next owner or decision

Quality Gates

  • Audio Goal
  • Asset Need
  • Mix Target
  • QA Note
  • Scope remains bounded to the current task and project stage.
  • Report labels unverified assumptions separately from evidence.

Decision Gates

  • Continue only when the expected output can be verified or clearly labeled as a plan.
  • Escalate to producer or qa-playtester when scope, ownership, or acceptance evidence is ambiguous.
  • Stop before broad rewrites, generated prompt mirrors, or hidden lifecycle behavior.

Handoff

Report changed files, verification evidence, remaining risks, and the next owner or decision. Do not imply hidden hooks or autonomous background work.