Menu
Inspect the repo state and show a status panel across all milestones, recommending the earliest actionable next step in the workflow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Enforce OOP and DDD engineering constraints for C# and TypeScript game development. Use when implementing, refactoring, reviewing, or testing gameplay systems, combat, inventory, progression, quests, scenes, matches, player data, save/load flows, domain-controlled engine-view wrappers, domain models, aggregates, application services, repositories, vertical slices, public APIs, Context-based shared dependencies, or deterministic test seams. Preserve encapsulation, keep engine details outside Domain, avoid test-only production hooks, and deliver complete game behavior through public contracts.
Design one system within a specific milestone's scope: write the milestone-scoped system GDD, content data, and system art doc, and update the milestone brief's progress. Requires a mandatory milestone argument.
Plan milestone slices from overview + narrative alone (no system GDDs required), create per-milestone directory skeletons and briefs, and write gat/milestone/milestone.md. Runs before per-system design. Stops before technical design, task breakdown, or implementation.
Generate images through OpenRouter's dedicated Image API. Use this skill whenever the user wants to create, render, generate, or save images with OpenRouter, including text-to-image, image-to-image/reference images, choosing OpenRouter image models, listing image models, setting resolution/aspect ratio/quality/output format, or passing provider-specific image options. Prefer the bundled Python script so API options are passed explicitly as command-line arguments instead of hand-written ad hoc curl requests.
Brainstorm a game idea through one-question-at-a-time designer interviews. Produces game.md, systems-index.md, and art-direction.md, or runs as discussion-only.
Develop game story and narrative through one-question-at-a-time writer interviews. Produces narrative docs under gat/narrative/ or runs as discussion-only. Use when the user wants story, plot, lore, worldbuilding, characters, quests, dialogue, narrative tone, or authored story content for a GAT game.
| name | gat-workflow-start |
| description | Inspect the repo state and show a status panel across all milestones, recommending the earliest actionable next step in the workflow. |
| argument-hint | [no arguments] |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, AskUserQuestion |
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.
Check for these files (all under gat/):
gat/overview/game.mdgat/overview/systems-index.mdgat/overview/art-direction.mdgat/narrative/*.mdgat/milestone/milestone.mdgat/milestone/m{N}-<name>/m{N}-brief.mdgat/milestone/m{N}-<name>/<system>/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 alldesigned — every in-scope system's GDD (and art/data where required) is on diskIf the brief's status field disagrees with filesystem state, derive the stage from filesystem state.
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)
...
Use earliest-first priority to pick the primary recommendation, and list other valid actions:
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.gat/narrative/story.md does not exist:
recommend /gat-story.gat/milestone/milestone.md is missing:
recommend /gat-milestone./gat-design <that milestone> (continue) or /gat-design <that milestone> <system>.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).Always also list other valid actions (e.g., "M1 ready for engineering; M2
designing — run /gat-design m2-<name> to continue M2").
End with one short line telling the user which command to run next (the primary recommendation), plus any alternative actions.