project-stage-detect

A project stage detection scan analyzes your design documents, source code structure, architecture docs, prototypes, and test signals to classify the current development phase. It identifies documentation gaps and asks targeted questions before generating an actionable stage report.

An artifact-based development audit assesses codebase milestone readiness by scanning production planning artifacts, architecture decisions, and test signals. It surfaces process gaps through targeted clarifying questions, ensuring you understand roadmap readiness before proceeding.

Yes, you can use an optional production/stage.txt file to override the automatic artifact-based stage classification. When this file is present, the skill uses your manual specification instead of scanning design documents and source code structure to infer the development stage.

Gap analysis for codebase onboarding scans existing design and architecture docs to identify missing artifacts, then asks targeted clarifying questions instead of assuming intent. It surfaces documentation and process gaps through a collaborative approval gate before writing an output report.

No, the project stage detection process follows a collaborative approval gate and does not write report artifacts automatically. It generates a structured stage analysis plan, asks clarifying questions to resolve gaps, and explicitly requests your approval before creating any output files.