project-stage-detect

Identify the project stage by scanning design, source, production, prototypes, and architecture artifacts. Apply heuristic rules to determine the stage and surface missing items, then propose actionable next steps tailored to the provided role. It loads configuration from repository structure and returns a structured stage report.

Missing items include absent design components in design/gdd, missing sprint plans or milestones in production artifacts, and incomplete codebase structures in src/ or core/. Scanning these artifacts surfaces gaps and generates clarifying questions to drive alignment across engineering, design, and production roles.

Yes, you can tailor the gap analysis by providing a role filter such as engineer, designer, or producer. The generated stage report adjusts its actionable next steps and clarifying questions to align specifically with the responsibilities of the provided role.

Assess design artifacts by scanning directories like design/gdd, narrative, and levels to evaluate documentation coverage. This scan identifies missing design components and generates a structured report with clarifying questions to ensure alignment before active development continues.

Yes, codebase structure directly affects stage detection. Inspecting source directories like src/, core/, gameplay/, ui/, and networking/ gauges structure size and active development signals, which heuristic rules use to determine the current development stage and surface missing items.

The best way to check for missing roadmaps is to review production directories, prototypes, and roadmap files. This inspection identifies absent sprint plans or milestones, surfacing gaps in production artifacts to generate a structured stage report with actionable next steps.