project-stage-detect

To analyze a codebase and determine its project stage, scan design documentation, source code, production artifacts, and tests to classify the phase and identify development gaps. This produces a stage classification with a prioritized gap list.

A project stage gap analysis reviews architecture, code, and milestones against expected artifacts to find missing components. You need it during onboarding, milestone planning, or project audits to clarify the development phase and guide next steps.

Yes, tailored recommendations are supported by passing an optional role parameter to the analysis. This adjusts the output to provide relevant next steps and clarifying questions suited to that specific role's perspective.

The best way to audit architecture is to evaluate source code directories alongside tests and Architecture Decision Records. This identifies major systems, estimates coverage, and checks for active sprint plans to produce a prioritized gap list.

Yes, project stage detection works without dependencies or external components. It directly scans existing repository artifacts like design docs, source code, and test files to evaluate the current development stage.

Your project lacks clear milestones if production artifacts are missing roadmaps or sprint plans. Find the gaps by scanning the production directory and generating a prioritized gap list with clarifying questions for collaborative decisions.