# Project Stage Detect

Analyze project state, detect stage, identify gaps, recommend next steps.

- Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (32144 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-19
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Donchitos/Claude-Code-Game-Studios --skill project-stage-detect -g -a claude-code -y`
Codex: `npx skills add Donchitos/Claude-Code-Game-Studios --skill project-stage-detect -g -a codex -y`
Cursor: `npx skills add Donchitos/Claude-Code-Game-Studios --skill project-stage-detect -g -a cursor -y`
Gemini CLI: `npx skills add Donchitos/Claude-Code-Game-Studios --skill project-stage-detect -g -a gemini-cli -y`

## Description

Analyze project state, detect stage, identify gaps, recommend next steps. 'Where are we in development?

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Project Stage Detection

This skill scans your project to determine its current development stage, completeness
of artifacts, and gaps that need attention. It's especially useful when:
- Starting with an existing project
- Onboarding to a codebase
- Checking what's missing before a milestone
- Understanding "where are we?"

---

## Workflow

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

**Automation mode**: Resolve `modes.automation` (`project.local.yaml` →
`project.yaml` → default `collaborative`). Every `AskUserQuestion` call and
every file write follows `.claude/docs/automation-modes.md`
(collaborative asks always · guided major-only · autonomous logs and proceeds;
`automation_always_ask` categories always prompt).

Resolved above, use as-is. No block → defaults in
`.claude/docs/config-resolution.md`.

> **Resolve the tier, do not assume it.** The tier decides what counts as a gap
> at all: at `full` every missing doc is one; at `minimal` none of them are,
> because a brief plus an engine is the normal state and code is the expected
> next step. Guessing high tells a jam project it is missing GDDs, an art bible
> and ADRs, the exact "process feels mismatched to my project" experience
> `modes.rigor` exists to prevent.

**`workflow`** (per `.claude/docs/workflow-modes.md`). The tier governs
which absent documents count as gaps (step 3), below `full`, optional docs are
not flagged.

### 1. Scan Key Directories

**Start with the deterministic pass, it answers "what exists" for every
catalogued artifact in one call:**

```
Bash: bash .claude/scripts/artifact-check.sh
```

Run it exactly as written, from the project root, relative path, no
arguments, no `cd`, no `2>&1`. This skill's permission grant matches that form;
any other asks the user to approve it.

The rest: https://github.com/Donchitos/Claude-Code-Game-Studios/blob/HEAD/.claude/skills/project-stage-detect/SKILL.md