Files
codex-game-studio/.agents/skills/cgs-propagate-design-change/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.6 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-propagate-design-change Use for propagate design change tasks that trace a design change through systems, docs, tasks, tests, content, and release risk; produce verification evidence, changed or proposed files, and handoff boundaries. gpt-5.6-terra high Describe the propagate-design-change objective, target files/assets, constraints, and verification evidence. producer read/edit/shell/tests/git as needed within the repository write policy repository-root; no init-time generated prompt bodies .claude/skills/propagate-design-change/SKILL.md eba7901d3875f81946ab8803f458d142427102c438296fae83e3f4c4101115ed true

Codex Game Studio Propagate Design Change

Use this skill for propagate design change work in Template Game.

Objective

Trace a design change through systems, docs, tasks, tests, content, and release risk.

Inputs

  • AGENTS.md
  • .codex/studio.json
  • task-relevant files named by the user or task record
  • design/gdd.md
  • docs/market-overview.md

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 trace a design change through systems, docs, tasks, tests, content, and release risk. and identify the current project stage.
  2. Collect evidence for Change Summary, Affected Systems, Required Updates.
  3. Draft or review the artifact in small sections, keeping player experience and scope visible.
  4. Produce the requested artifact or review with clear file paths and verification evidence.

Write Targets

  • design/

Output Contract

  • Summary
  • Change Summary
  • Affected Systems
  • Required Updates
  • Regression Risk
  • Risks
  • Changed files or proposed files
  • Verification evidence
  • Next owner or decision

Quality Gates

  • Change Summary
  • Affected Systems
  • Required Updates
  • Regression Risk
  • 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.