project-stage-detect

To audit your game's development stage, the Skill scans design documents, source code structure, architecture records, and prototypes to infer current progress. It generates a completeness-focused report highlighting gaps and asking clarifying questions about weak areas.

Yes, you can override the detected project stage manually by providing an explicit stage definition in the production/stage.txt file. The heuristic classification process checks this optional file before scanning directory artifacts to determine your game's current development phase.

Milestone readiness checks evaluate your existing production artifacts, prototypes, and tests against expected development stages. The Skill applies deterministic directory scanning to classify progress and outputs a structured stage analysis with prioritized next steps for your team.

Yes, onboarding to an existing codebase is a core scenario supported by the stage detection tool. It analyzes the source code structure and architecture records to provide role-filtered recommendations, helping new team members understand the project's current development phase.

Gap analysis for game development evaluates existing repository artifacts against expected milestones to classify project progress heuristically. Rather than assuming missing elements, it identifies weak areas in your production pipeline and asks clarifying questions to refine the completeness assessment.

No, the stage detection process uses a collaborative reporting workflow that requests approval before writing any new files. It generates a structured stage analysis using a specific report template but ensures you maintain control over repository modifications.