Workflow Start

Codex Runtime

This skill is fully contained in the installed .agents directory. Resolve all linked resources relative to this SKILL.md; do not read workflow resources outside this packaged directory.

Before inspecting project state, read GAT Workflow, Directory Structure, and Workflow Catalog.

Treat the directory containing .agents as the repository root. All GAT project documents live under that root's gat/ directory. Use Codex filesystem tools and the environment's supported patch editor while preserving unrelated user changes.

Interpret AskUserQuestion in the procedure as a single concise user question. Use a structured choice UI only for a genuine 2-3 option decision; otherwise ask in ordinary dialogue and wait. Command examples use Codex skill syntax ($gat-*).

This skill is the workflow router for the simplified project. Because milestones can be in progress at different stages at the same time, it outputs a status panel (not a single command) and recommends the earliest actionable step.

Read only gat/ paths. Do not read or consider legacy design/ or production/ paths.

Phase 1: Inspect State

Check for these files (all under gat/):

• gat/overview/game.md
• gat/overview/systems-index.md
• gat/overview/art-direction.md
• gat/narrative/*.md
• gat/milestone/milestone.md
• each gat/milestone/m{N}-<name>/m{N}-brief.md
• each system's docs under gat/milestone/m{N}-<name>/<system>/

Phase 2: Derive Per-Milestone Stage

For each milestone that has an m{N}-brief.md, derive its stage from filesystem state:

• planned — brief exists, all systems Pending (no GDDs on disk)
• designing — at least one system designed but not all
• designed — every in-scope system's GDD (and art/data where required) is on disk

If the brief's status field disagrees with filesystem state, derive the stage from filesystem state.

Phase 3: Status Panel

Report a short factual summary:

GAT Status:

Overview:
  gat/overview/game.md          [present | missing]
  gat/overview/systems-index.md [present | missing]
  gat/overview/art-direction.md [present | missing]

Narrative:
  gat/narrative/*.md            [N docs | missing]

Milestones (from gat/milestone/milestone.md):
  M1 <name>   [planned | designing | designed]  (K/N systems designed)
  M2 <name>   [planned | designing | designed]  (K/N systems designed)
  ...

Phase 4: Route

Use earliest-first priority to pick the primary recommendation, and list other valid actions:

1. If gat/overview/game.md, gat/overview/systems-index.md, or gat/overview/art-direction.md is missing: recommend $gat-brainstorm (with optional hint). This is the earliest step.
2. Else if the game needs narrative (per overview/user goal) and gat/narrative/story.md does not exist: recommend $gat-story.
3. Else if gat/milestone/milestone.md is missing: recommend $gat-milestone.
4. Else if the earliest milestone with unwritten systems exists: recommend $gat-design <that milestone> (continue) or $gat-design <that milestone> <system>.
5. Else if the earliest milestone is fully designed but no later milestone needs design: state that the milestone is ready for engineering handoff (the user runs their downstream engineering workflow on that milestone directory; the brief includes detailed internal iterations for the downstream workflow to handle).
6. Otherwise: state that GAT pre-production is complete for all planned milestones and tell the user to hand milestones one at a time to their downstream engineering workflow.

Always also list other valid actions (e.g., "M1 ready for engineering; M2 designing — run $gat-design m2-<name> to continue M2").

Phase 5: Hand Off

End with one short line telling the user which command to run next (the primary recommendation), plus any alternative actions.