help

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Studio Help — What Do I Do Next?

Studio Help — 我接下来该做什么？

This skill is read-only — it reports findings but writes no files.

This skill figures out exactly where you are in the game development pipeline and tells you what comes next. It is lightweight — not a full audit. For a full gap analysis, use

/project-stage-detect

此技能为只读模式——它仅报告结果，不写入任何文件。

该技能可准确判断你在游戏开发流程中的当前位置，并告知下一步操作。它轻量便捷——并非完整审计。如需全面的差距分析，请使用

/project-stage-detect

。

Step 1: Read the Catalog

步骤1：阅读目录

Read

.claude/docs/workflow-catalog.yaml

. This is the authoritative list of all phases, their steps (in order), whether each step is required or optional, and the artifact globs that indicate completion.

阅读

.claude/docs/workflow-catalog.yaml

。这是所有阶段、步骤（按顺序排列）、各步骤是否必填或可选，以及表明完成状态的工件通配符的权威列表。

Step 1b: Find Skills Not in the Catalog

步骤1b：查找目录中未收录的技能

After reading the catalog, Glob

.claude/skills/*/SKILL.md

to get the full list of installed skills. For each file, extract the

name:

field from its frontmatter.

Compare against the

command:

values in the catalog. Any skill whose name does not appear as a catalog command is an uncataloged skill — still usable but not part of the phase-gated workflow.

Collect these for the output in Step 7 — show them as a footer block:

undefined

阅读目录后，使用 Glob 匹配

.claude/skills/*/SKILL.md

，获取已安装技能的完整列表。对于每个文件，从其前置元数据中提取

name:

字段。

与目录中的

command:

值进行对比。任何名称未出现在目录命令中的技能均为未收录技能——仍可使用，但不属于阶段管控工作流的一部分。

收集这些信息用于步骤7的输出——在页脚块中展示：

undefined

Also installed (not in workflow)

已安装但未纳入工作流的技能

```
/skill-name
```
— [description from SKILL.md frontmatter]
```
/skill-name
```
— [description]


Only show this block if at least one uncataloged skill exists. Limit to the 10
most relevant based on the user's current phase (QA skills in production, team
skills in production/polish, etc.).

---

```
/skill-name
```
— [来自SKILL.md前置元数据的描述]
```
/skill-name
```
— [描述]


仅当存在至少一个未收录技能时才显示此块。根据用户当前阶段选择最相关的10个技能（例如生产阶段的QA技能、生产/打磨阶段的团队技能等）。

---

Step 2: Determine Current Phase

步骤2：确定当前阶段

Check in this order:

Read
production/stage.txt
— if it exists and has content, this is the authoritative phase name. Map it to a catalog phase key:
- "Concept" →
```
concept
```
- "Systems Design" →
```
systems-design
```
- "Technical Setup" →
```
technical-setup
```
- "Pre-Production" →
```
pre-production
```
- "Production" →
```
production
```
- "Polish" →
```
polish
```
- "Release" →
```
release
```

If stage.txt is missing, infer phase from artifacts (most-advanced match wins):

```
src/
```
has 10+ source files →
```
production
```
```
production/stories/*.md
```
exists →
```
pre-production
```

docs/architecture/adr-*.md

exists →

technical-setup

design/gdd/systems-index.md

exists →

systems-design

```
design/gdd/game-concept.md
```
exists →
```
concept
```
Nothing →
```
concept
```
(fresh project)

按以下顺序检查：

读取
production/stage.txt
——如果该文件存在且有内容，这是权威的阶段名称。将其映射到目录阶段键：
- "Concept" →
```
concept
```
  （概念阶段）
- "Systems Design" →
```
systems-design
```
  （系统设计阶段）
- "Technical Setup" →
```
technical-setup
```
  （技术搭建阶段）
- "Pre-Production" →
```
pre-production
```
  （预生产阶段）
- "Production" →
```
production
```
  （生产阶段）
- "Polish" →
```
polish
```
  （打磨阶段）
- "Release" →
```
release
```
  （发布阶段）
若stage.txt缺失，从工件推断阶段（匹配最先进的阶段获胜）：
- ```
src/
```
  包含10个以上源文件 →
```
production
```
  （生产阶段）
- ```
production/stories/*.md
```
  存在 →
```
pre-production
```
  （预生产阶段）
- ```
docs/architecture/adr-*.md
```
  存在 →
```
technical-setup
```
  （技术搭建阶段）
- ```
design/gdd/systems-index.md
```
  存在 →
```
systems-design
```
  （系统设计阶段）
- ```
design/gdd/game-concept.md
```
  存在 →
```
concept
```
  （概念阶段）
- 无任何文件 →
```
concept
```
  （新项目）

Step 3: Read Session Context

步骤3：读取会话上下文

Read

production/session-state/active.md

if it exists. Extract:

What was most recently worked on
Any in-progress tasks or open questions
Current epic/feature/task from STATUS block (if present)

This tells you what the user just finished or is stuck on — use it to personalize the output.

如果存在

production/session-state/active.md

，请读取该文件。提取：

最近处理的工作内容
任何进行中的任务或未解决的问题
STATUS块中的当前史诗/功能/任务（如有）

这能让你了解用户刚刚完成的工作或卡住的点——据此个性化输出内容。

Step 4: Check Step Completion for the Current Phase

步骤4：检查当前阶段的步骤完成情况

For each step in the current phase (from the catalog):

针对当前阶段的每个步骤（来自目录）：

Artifact-based checks

基于工件的检查

If the step has

artifact.glob

Use Glob to check if files matching the pattern exist
If
```
min_count
```
is specified, verify at least that many files match
If
```
artifact.pattern
```
is specified, use Grep to verify the pattern exists in the matched file
Complete = artifact condition is met
Incomplete = artifact is missing or pattern not found

If the step has

artifact.note

(no glob):

Mark as MANUAL — cannot auto-detect, will ask user

If the step has no

artifact

field:

Mark as UNKNOWN — completion not trackable (e.g. repeatable implementation work)

如果步骤包含

artifact.glob

：

使用 Glob 检查是否存在匹配该模式的文件
如果指定了
```
min_count
```
，验证至少有对应数量的文件匹配
如果指定了
```
artifact.pattern
```
，使用 Grep 验证匹配文件中存在该模式
已完成 = 满足工件条件
未完成 = 工件缺失或未找到匹配模式

如果步骤包含

artifact.note

（无通配符）：

标记为MANUAL（手动）——无法自动检测，需询问用户

如果步骤无

artifact

字段：

标记为UNKNOWN（未知）——无法跟踪完成状态（例如可重复的实现工作）

Special case: production phase — read

sprint-status.yaml

特殊情况：生产阶段——读取

sprint-status.yaml

When the current phase is

production

, check for

production/sprint-status.yaml

before doing any glob-based story checks. If it exists, read it directly:

Stories with
```
status: in-progress
```
→ surface as "currently active"
Stories with
```
status: ready-for-dev
```
→ surface as "next up"
Stories with
```
status: done
```
→ count as complete
Stories with
```
status: blocked
```
→ surface as blocker with the
```
blocker
```
field

This gives precise per-story status without markdown scanning. Skip the glob artifact check for the

implement

and

story-done

steps — the YAML is authoritative.

当当前阶段为

production

时，在进行任何基于通配符的故事检查之前，先检查是否存在

production/sprint-status.yaml

。如果存在，直接读取：

```
status: in-progress
```
的故事 → 标记为“当前进行中”
```
status: ready-for-dev
```
的故事 → 标记为“下一步待处理”
```
status: done
```
的故事 → 计为已完成
```
status: blocked
```
的故事 → 标记为阻塞项，并展示
```
blocker
```
字段内容

这无需扫描Markdown即可提供精确的每个故事状态。跳过

implement

和

story-done

步骤的通配符工件检查——该YAML文件为权威依据。

Special case:

repeatable: true

(non-production)

特殊情况：

repeatable: true

（非生产阶段）

For repeatable steps outside production (e.g. "System GDDs"), the artifact check tells you whether any work has been done, not whether it's finished. Label these differently — show what's been detected, then note it may be ongoing.

对于生产阶段之外的可重复步骤（例如“系统GDD”），工件检查仅能告诉你是否已开展相关工作，而非是否已完成。需对这些步骤进行不同标记——展示已检测到的内容，然后注明工作可能仍在进行中。

Step 5: Find Position and Identify Next Steps

步骤5：确定位置并识别下一步

From the completion data, determine:

Last confirmed complete step — the furthest completed required step
Current blocker — the first incomplete required step (this is what the user must do next)
Optional opportunities — incomplete optional steps that can be done before or alongside the blocker
Upcoming required steps — required steps after the current blocker (show as "coming up" so user can plan ahead)

If the user provided an argument (e.g. "just finished design-review"), use that to advance past the step they named even if the artifact check is ambiguous.

根据完成数据，确定：

最后一个已确认完成的步骤——完成度最高的必填步骤
当前阻塞项——第一个未完成的必填步骤（这是用户接下来必须完成的任务）
可选机会——当前可完成的未完成可选步骤，可在处理阻塞项之前或同时进行
即将到来的必填步骤——当前阻塞项之后的必填步骤（标记为“即将到来”，方便用户提前规划）

如果用户提供了参数（例如“刚完成设计评审”），即使工件检查结果不明确，也可据此跳过用户提及的步骤。

Step 6: Check for In-Progress Work

步骤6：检查进行中的工作

active.md

shows an active task or epic:

Surface it prominently at the top: "It looks like you were working on [X]"
Suggest continuing it or confirm if it's done

如果

active.md

显示有进行中的任务或史诗：

在顶部突出显示：“看起来你正在处理 [X]”
建议继续该任务或确认是否已完成

Step 7: Present Output

步骤7：呈现输出

Keep it short and direct. This is a quick orientation, not a report.

undefined

保持简洁直接。这是快速定位工具，而非详细报告。

undefined

Where You Are: [Phase Label]

当前位置：[阶段名称]

In progress: [from active.md, if any]

进行中： [来自active.md的内容（如有）]

✓ Done

✓ 已完成

[completed step name]
[completed step name]

[已完成步骤名称]
[已完成步骤名称]

→ Next up (REQUIRED)

→ 下一步（必填）

[Step name] — [description] Command:

[/command]

[步骤名称] — [描述] 命令：

[/command]

~ Also available (OPTIONAL)

~ 可选操作

[Step name] — [description] →
```
/command
```
[Step name] — [description] →
```
/command
```

[步骤名称] — [描述] →
```
/command
```
[步骤名称] — [描述] →
```
/command
```

Coming up after that

后续即将开展

[Next required step name] (
```
/command
```
)
[Next required step name] (
```
/command
```
)

Approaching [next phase] gate → run

/gate-check

when ready.


**Formatting rules:**
- `✓` for confirmed complete
- `→` for the current required next step (only one — the first blocker)
- `~` for optional steps available now
- Show commands inline as backtick code
- If a step has no command (e.g. "Implement Stories"), explain what to do instead of showing a slash command
- For MANUAL steps, ask the user: "I can't tell if [step] is done — has it been completed?"

Verdict: **COMPLETE** — next steps identified.

---

[下一个必填步骤名称] (
```
/command
```
)
[下一个必填步骤名称] (
```
/command
```
)

即将进入**[下一阶段]**关卡 → 准备就绪时运行

/gate-check

。


**格式规则：**
- `✓` 表示已确认完成
- `→` 表示当前必填的下一步（仅一个——第一个阻塞项）
- `~` 表示当前可用的可选步骤
- 命令以反引号代码块形式内联展示
- 如果步骤无命令（例如“实现故事”），则说明具体操作而非展示斜杠命令
- 对于MANUAL（手动）步骤，询问用户：“我无法判断[步骤]是否已完成——是否已经完成？”

结论：**COMPLETE（完成）**——已确定下一步操作。

---

Step 8: Gate Warning (if close)

步骤8：关卡提醒（若临近）

After the current phase's steps, check if the user is likely approaching a gate:

If all required steps in the current phase are complete (or nearly complete), add: "You're close to the [Current] → [Next] gate. Run
```
/gate-check
```
when ready."
If multiple required steps remain, skip the gate warning — it's not relevant yet.

在当前阶段的步骤之后，检查用户是否即将进入关卡：

如果当前阶段的所有必填步骤已完成（或接近完成），添加：“你即将进入**[当前阶段] → [下一阶段]**关卡。准备就绪时运行
```
/gate-check
```
。”
如果仍有多个必填步骤未完成，跳过关卡提醒——此时无关紧要。

Step 9: Escalation Paths

步骤9：升级路径

After the recommendations, if the user seems stuck or confused, add:

---
Need more detail?
- `/project-stage-detect` — full gap analysis with all missing artifacts listed
- `/gate-check` — formal readiness check for your next phase
- `/start` — re-orient from scratch

Only show this if the user's input suggested confusion (e.g. "I don't know", "stuck", "lost", "not sure"). Don't show it for simple "what's next?" queries.

在给出建议后，如果用户似乎卡住或感到困惑，添加：

---
需要更多细节？
- `/project-stage-detect` — 完整差距分析，列出所有缺失的工件
- `/gate-check` — 针对下一阶段的正式就绪检查
- `/start` — 从头重新定位

仅当用户的输入表明存在困惑时（例如“我不知道”“卡住了”“迷路了”“不确定”）才展示此内容。对于简单的“下一步是什么？”查询，无需展示。

Collaborative Protocol

协作协议

Never auto-run the next skill. Recommend it, let the user invoke it.
Ask about MANUAL steps rather than assuming complete or incomplete.
Match the user's tone — if they sound stressed ("I'm totally lost"), be reassuring and give one action, not a list of six.
One primary recommendation — the user should leave knowing exactly one thing to do next. Optional steps and "coming up" are secondary context.

切勿自动运行下一个技能。仅提供建议，由用户自行调用。
询问手动步骤的完成情况，而非假设已完成或未完成。
匹配用户语气——如果用户听起来压力很大（例如“我完全迷路了”），请保持安抚，并仅给出一个操作建议，而非六个列表项。
一个主要建议——用户离开时应明确知道接下来要做的一件事。可选步骤和“即将到来”的内容为次要信息。