project-stage-detect

Auditing your repository stage involves scanning design docs, source code, architecture decision records, production plans, prototypes, and tests to estimate completeness and infer the current lifecycle stage using backward heuristics.

A project stage detection heuristic infers your project's lifecycle phase, from Concept to Release, by examining existing artifacts. You need it during onboarding, milestone preparation, or existing-project audits to identify missing documentation before investing more effort.

Yes, you can override the detected development stage by creating an explicit `production/stage.txt` file in your repository. The audit will read this file directly instead of relying on backward heuristics to infer your project's phase.

To identify gaps in architecture decision records and documentation completeness, the skill generates a stage report draft and produces clarifying questions for each detected missing artifact, asking for approval before writing any new files.

Yes, the project audit tool optionally tailors next-step recommendations by filtering priorities for programmers, designers, or producers, ensuring the generated stage report template aligns with your specific team role's requirements.