Studio Help, What Do I Do Next?

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.

Live Project State

!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys project.stage,workflow

These are resolved before this skill runs. Use them as-is:

• project.stage from the config block is the authoritative phase for Step 2, it already applies the project.yaml → production/stage.txt fallback, and preserves values containing spaces (Systems Design).
• workflow from the config block is the tier for Steps 2 and 5, do not re-read it.
• If no config block rendered, shell preprocessing is disabled; fall back to the defaults in .claude/docs/config-resolution.md.

---

Step 1: Read the Catalog

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.

---

Step 1b: Find Skills Not in the Catalog

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:

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

---