codex-game-studio/.codex/workflows/implement.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-terra	medium	gameplay-programmer	cgs-dev-story cgs-standards-gameplay	implement	high	Provide an implementation request with accepted design context, exact target files or artifacts, scope constraints, owner or handoff needs, and required verification evidence.	.codex/workflows/implement.md	ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff	plan changed-files verification-evidence handoff

Implement Workflow

Purpose

Implement a bounded feature slice from accepted design context with changed files, validation evidence, risks, and handoff notes.

Inputs

• AGENTS.md
• .codex/studio.json
• .codex/workflows/implement.md
• Accepted feature spec, GDD context, target source files, and test commands

Role

Gameplay Programmer (gameplay-programmer) owns this workflow.

Taxonomy

Category: implementation-planning CCGS adaptation coverage:

• implementation execution
• bounded feature delivery CLI aliases:
• implement

Outputs

• Minimal source, test, or asset changes needed for the requested slice.
• Verification command output and changed-file summary.
• Risks, follow-up tasks, and handoff notes.

Validation

• Implementation remains within the accepted scope.
• Tests or manual verification prove the changed behavior.
• Engine conventions and rollback risks are addressed.

Phase Gates

• Confirm project state, owner role, write policy, and selected context.
• Name required artifacts and 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, docs, release notes, or tests 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.

Documentation Impact

• After functional source, engine, or asset changes, update the owning game document or record a fresh ## Documentation Impact decision in production/session-state/active.md.
• Run ./codex-game-studio docs-impact --base <review-base> before handoff.
• A no-update decision must state why no player, architecture, production, or release document changed.