codex-game-studio/.codex/workflows/ship-check.md

model, model_reasoning_effort, primary-agent, linked-skills, phase, risk, argument-hint, source-reference, source-hash, output-artifacts

model	model_reasoning_effort	primary-agent	linked-skills	phase	risk	argument-hint	source-reference	source-hash	output-artifacts
gpt-5.6-sol	high	release-manager	cgs-standards-gameplay cgs-vertical-slice	ship	high	Provide a ship check request with the objective or decision, target files/assets/milestone, scope constraints, owner or handoff needs, and required verification evidence.	.codex/workflows/ship-check.md	c0314e1b40f51a412fb34e841c4828b18841d12d524e73578609f2f8b946877d	plan changed-files verification-evidence handoff

Ship Check Workflow

Purpose

Assess milestone readiness, package risk, validation status, and release blockers.

Inputs

• AGENTS.md
• .codex/studio.json
• .codex/workflows/ship-check.md
• production/timeline.md

Role

Release Manager (release-manager) owns this workflow.

Taxonomy

Category: release-hotfix CCGS adaptation coverage:

• ship readiness
• release blocker review

CLI aliases:

• none

Outputs

• Ship checklist
• Release risks
• Validation summary

Validation

• Blockers are separated from warnings
• Validation is current
• Packaging risks are explicit

Phase Gates

• Confirm project state, owner role, write policy, and selected context.
• Name acceptance criteria before implementation or review work.
• Do not advance to handoff until evidence is recorded or a blocker is explicit.

Required Artifacts

• Summary of the workflow result.
• Files, assets, tasks, or docs changed or proposed.
• Verification evidence and unresolved risks.

Context Contract

• Load AGENTS.md, .codex/studio.json, this workflow, the primary agent, linked skills, and only task-relevant project files.
• Avoid broad context unless the user explicitly approves it.

Output Contract

• Decision or change summary.
• Step-by-step work performed or planned.
• Evidence, blockers, warnings, and next owner.

Stop Conditions

• Required project state, approval, target files, or verification path is missing.
• The task crosses into another role without an explicit handoff.
• The workflow would require generated prompt mirrors or hidden automation.

Handoff

Report changed files, validation evidence, residual risks, and the next owner only when ownership changes.