菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | gat-milestone |
| description | 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. |
| argument-hint | [optional planning focus] |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Write, Edit, Agent, AskUserQuestion |
This skill plans milestone slices BEFORE per-system design and creates:
gat/milestone/milestone.md — the ordered milestone roadmap with statusgat/milestone/m{N}-<name>/ — per-milestone directory skeletonsgat/milestone/m{N}-<name>/m{N}-brief.md — milestone brief skeletons (all systems Pending, status planned)It does NOT require any system GDD to exist. It does not create task lists, technical designs, prompt packs, or implementation files. Those belong to the downstream engineering workflow.
Fail if any of these are missing:
gat/overview/game.mdgat/overview/systems-index.mdgat/overview/art-direction.mdDo NOT fail when no system GDDs exist. Planning runs before design; the systems index's priorities and dependencies are sufficient input for slicing.
Read:
gat/overview/game.mdgat/overview/systems-index.mdgat/overview/art-direction.mdgat/narrative/*.md (used to inform milestone boundaries).claude/docs/templates/plan/milestone.md.claude/docs/templates/plan/m-brief.mdgat/milestone/milestone.md if it already existsgat/milestone/m{N}-<name>/m{N}-brief.md files if any milestones are already plannedSpawn gat-planner agent with all read content plus:
gat/milestone/milestone.md as an ordered set of milestone slices (M01, M02, ...) with a status column (planned -> designing -> designed)gat/milestone/m{N}-<name>/ for each planned milestonem{N}-brief.md skeleton (template: .claude/docs/templates/plan/m-brief.md) for each milestone, listing every in-scope system with status Pending and the milestone status plannedThe planner should:
plannedSummarize how many milestones were planned, which comes first, and which directories/briefs were created.
Use AskUserQuestion:
Start designing the first milestone (Recommended) → Tell the user to run /gat-design <first-milestone> <system> or /gat-design <first-milestone> (continue)Stop hereEnforce 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.
Inspect the repo state and show a status panel across all milestones, recommending the earliest actionable next step in the workflow.
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.