Menu
Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts. Use when user asks 'where are we in development', 'what stage are we in', 'full project audit'.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /ags-design-review.
Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.
Brownfield onboarding โ audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /ags-project-stage-detect (which checks what exists) โ this checks whether what exists will actually work with the template's skills.
Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.
Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /ags-brainstorm is approved and before /ags-map-systems or any GDD authoring begins.
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
| name | ags-project-stage-detect |
| description | Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts. Use when user asks 'where are we in development', 'what stage are we in', 'full project audit'. |
| argument-hint | [optional: role filter like 'programmer' or 'designer'] |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Bash, Write, AskUserQuestion |
| model | haiku |
Language: Talk to user in language from .ags/project/user-interaction.md. Fall back to English if file missing. Files on disk always English per .ags/rules/user-interaction.md.
Scans project to determine current development stage, artifact completeness, and gaps. Useful for: starting with existing project, onboarding, pre-milestone check, or "where are we?"
| Artifact | Created by | If missing |
|---|---|---|
.ags/rules/workflow-catalog.yaml | template | STOP. "Workflow catalog missing โ broken install." |
If STOP triggers, exit verdict BLOCKED.
Analyze project structure and content:
Design Documentation (design/):
design/gdd/*.mddesign/narrative/design/levels/Source Code (Assets/Scripts/):
Production Artifacts (.ags/project/):
Architecture Docs (design/architecture/):
Tests (tests/):
Based on scanned artifacts, determine stage. Check .ags/project/stage.md first โ
if it exists, use its value (explicit override from /ags-gate-check). Otherwise,
auto-detect using these heuristics (check from most-advanced backward):
| Stage | Indicators |
|---|---|
| Concept | No game concept doc, brainstorming phase |
| Systems Design | Game concept exists, systems index missing or incomplete |
| Technical Setup | Systems index exists, engine not configured |
| Pre-Production | Engine configured, Assets/Scripts/ has <10 source files |
| Production | Assets/Scripts/ has 10+ source files, active development |
| Polish | Explicit only (set by /ags-gate-check Production โ Polish gate) |
| Release | Explicit only (set by /ags-gate-check Polish โ Release gate) |
DO NOT just list missing files. Instead, ask clarifying questions:
Assets/Scripts/Gameplay/combat/) but no design/gdd/combat-system.md. Should we reverse-document it?".ags/project/. Are you tracking work elsewhere (Jira, Trello, etc.)?"/ags-map-systems?"Use template: .ags/templates/project-stage-report.md
Report structure:
# Project Stage Analysis
**Date**: [date]
**Stage**: [Concept/Systems Design/Technical Setup/Pre-Production/Production/Polish/Release]
**Stage Confidence**: [PASS โ clearly detected / CONCERNS โ ambiguous signals / FAIL โ critical gaps block progress]
## Completeness Overview
- Design: [X%] ([N] docs, [gaps])
- Code: [X%] ([N] files, [systems])
- Architecture: [X%] ([N] ADRs, [gaps])
- Production: [X%] ([status])
- Tests: [X%] ([coverage estimate])
## Gaps Identified
1. [Gap description + clarifying question]
2. [Gap description + clarifying question]
## Recommended Next Steps
[Priority-ordered list based on stage and role]
If user provided a role argument (e.g., /ags-project-stage-detect programmer):
Programmer:
Designer:
Producer:
General (no role):
Collaborative protocol:
I've analyzed your project. Here's what I found:
[Show summary]
Gaps identified:
1. [Gap 1 + question]
2. [Gap 2 + question]
Recommended next steps:
- [Priority 1]
- [Priority 2]
- [Priority 3]
May I write the full stage analysis to .ags/project/project-stage-report.md?
Wait for user approval before creating the file.
# General project analysis
/ags-project-stage-detect
# Programmer-focused analysis
/ags-project-stage-detect programmer
# Designer-focused analysis
/ags-project-stage-detect designer
After generating the report, suggest relevant next steps:
/ags-map-systems to decompose into systems/ags-reverse-document design Assets/Scripts/[system]/ags-architecture-decision or /ags-reverse-document architecture/ags-create-epics/ags-milestone-reviewNEVER silently write files. ALWAYS show findings and ask before creating artifacts.