gat-planlisted

# Plan This skill writes for one milestone: - `production/milestone-xx-name/tasks.md` - `production/milestone-xx-name/tech.md` - `production/milestone-xx-name/art-prompts.md` ## Phase 1: Validate Inputs Fail if any of these are missing: - `design/gdd/game.md` - `design/gdd/systems-index.md` - `production/milestone.md` Read: - `design/gdd/game.md` - `design/gdd/systems-index.md` - all existing `design/gdd/*.md` except `game.md` and `systems-index.md` - `design/art/art-direction.md` if exists - all existing `design/art/*-art.md` - `production/milestone.md` - `.claude/docs/templates/plan/tasks.md` - `.claude/docs/templates/plan/tech.md` - `.claude/docs/templates/plan/art-prompts.md` Resolve the target milestone: - If argument identifies a milestone, use it - Otherwise choose the first milestone directory that lacks `tasks.md` - If all have `tasks.md`, choose the first lacking `tech.md` Stop if no milestone can be resolved. Read existing milestone files if present: - `production/milestone-xx-name/tasks.md` - `production/milestone-xx-name/tech.md` - `production/milestone-xx-name/art-prompts.md` ## Phase 2: Spawn Planner Spawn `gat-planner` agent to write `tasks.md`: - Pass game overview, systems index, system GDDs, milestone roadmap - Pass selected milestone identity and directory - Pass tasks template and existing tasks.md if any - Instruction: define build order, create small programmer-owned tasks, make dependencies explicit, include verification notes per task