mirror of
https://github.com/merlinhu1/codex-game-studio.git
synced 2026-08-25 07:54:34 +02:00
7e8846a7fb
* 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>
2.6 KiB
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-create-control-manifest | Use for create control manifest tasks that define implementation rules, boundaries, allowed dependencies, validation commands, and review gates; produce verification evidence, changed or proposed files, and handoff boundaries. | gpt-5.6-luna | medium | Describe the create-control-manifest 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/create-control-manifest/SKILL.md | 2dd8d29c013944aed8cd05fcfbe21dc77ef8ff9c98f5155f46cee29ab3284348 | true |
Codex Game Studio Create Control Manifest
Use this skill for create control manifest work in Template Game.
Objective
Define implementation rules, boundaries, allowed dependencies, validation commands, and review gates.
Inputs
- AGENTS.md
- .codex/studio.json
- task-relevant files named by the user or task record
- docs/architecture/README.md
- design/gdd.md
Arguments
- Objective or user request.
- Target files, scenes, assets, or docs.
- Constraints, deadlines, acceptance criteria, and verification command when known.
Procedure
- Clarify the requested define implementation rules, boundaries, allowed dependencies, validation commands, and review gates. and identify the current project stage.
- Collect evidence for Layer Rules, Allowed Dependency, Validation Command.
- Compare options, choose the smallest reversible technical path, and record consequences.
- Produce the requested artifact or review with clear file paths and verification evidence.
Write Targets
- docs/architecture/
Output Contract
- Summary
- Layer Rules
- Allowed Dependency
- Validation Command
- Review Gate
- Risks
- Changed files or proposed files
- Verification evidence
- Next owner or decision
Quality Gates
- Layer Rules
- Allowed Dependency
- Validation Command
- Review Gate
- 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.