Gat workflow start

Skill Yuki001/game-dev-skills/gat/.claude/skills/gat-workflow-start

My personal agent skill repository, primarily focused on game development.

Install

npx -y skills add Yuki001/game-dev-skills --skill gat-workflow-start

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Inspect the repo state and show a status panel across all milestones, recommending the earliest actionable next step in the workflow.

SKILL.md

3.3 KB, as published. Nobody here has run it

Workflow Start

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:

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.
Else if the game needs narrative (per overview/user goal) and gat/narrative/story.md does not exist: recommend /gat-story.
Else if gat/milestone/milestone.md is missing: recommend /gat-milestone.
Else if the earliest milestone with unwritten systems exists: recommend /gat-design <that milestone> (continue) or /gat-design <that milestone> <system>.
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).
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.