project-stage-detect

Analyzes project artifacts to detect development stage, identify gaps, and recommend next steps.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill project-stage-detect-onemanking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-stage-detect
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/project-stage-detect
Command: npx skills add https://github.com/onemanking/the-operator --skill project-stage-detect-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When joining an existing codebase or checking progress before a milestone, it is hard to know where a project actually stands. This Skill scans design docs, source code, tests, and production artifacts to classify the development stage and surface missing pieces. ## Core Features & Use Cases - Stage Classification: Detects whether a project is in Concept, Systems Design, Technical Setup, Pre-Production, Production, Polish, or Release based on artifact heuristics and an optional explicit stage override file. - Collaborative Gap Analysis: Identifies missing GDDs, ADRs, sprint plans, and test coverage, then asks clarifying questions instead of assuming. - Role-Filtered Recommendations: Tailors next-step priorities for programmers, designers, producers, or general reviewers. - Use Case: Onboarding to a game project with scattered docs and code, run the analysis to get a completeness report and an approval-gated stage report written to production/. ## Quick Start Ask the assistant to analyze the current project state and detect its development stage, optionally specifying a role like programmer or designer.

Frequently Asked Questions about project-stage-detect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect what development stage my project is in?

Run the project stage detection analysis, which scans design docs, source code, tests, and production artifacts, then classifies the project into stages from Concept through Release using artifact-count heuristics or an explicit stage.txt override.

How to find missing documentation in a game project?

The analysis counts GDD files, ADRs, narrative docs, and sprint plans, then compares them against code systems to surface gaps. It asks clarifying questions, such as whether undocumented code was prototyped first, rather than assuming intent.

Can I filter project analysis recommendations by role?

Yes, pass a role argument such as programmer, designer, or producer. Programmers get architecture and test-coverage focus, designers get GDD completeness, and producers get sprint plan and milestone tracking recommendations.

Does the stage detection write files automatically?

No, it follows a collaborative protocol that shows findings and a report summary first, then waits for explicit user approval before writing the stage report to production/project-stage-report.md.

What are the limitations of heuristic stage detection?

Heuristics rely on artifact counts and directory conventions, so unconventional project layouts may misclassify. Polish and Release stages cannot be auto-detected and require an explicit stage.txt value set by a gate-check process.