gat-workflow-start

# 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 |...