Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/project-stage-detect
Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts.
Passed 7 of 13 test cases with the skill, and 3 of 13 without it.
and 6 more in the full report
8 fixed4 passed either way9 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
When the user approves saving the generated project stage analysis report, to what exact file path should the document be written?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies production/project-stage-report.md as the target report path. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill scans your project to determine its current development stage, completeness of artifacts, and gaps that need attention. It's especially useful when:
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys workflow,automation
Automation mode: Resolve modes.automation (project.local.yaml →
project.yaml → default collaborative). Every AskUserQuestion call and
every file write follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Resolved above — use as-is. No block → defaults in
.claude/docs/config-resolution.md.
Resolve the tier — do not assume it. Saying "surface gaps per the resolved workflow tier" without resolving it — no bootstrap, no helper call — leaves the tier as whatever the model assumed. The tier decides what counts as a gap at all: at
fullevery missing doc is one; atminimalnone of them are, because a brief plus an engine is the normal state and code is the expected next step. Guessing high tells a jam project it is missing GDDs, an art bible and ADRs — the exact "process feels mismatched to my project" experiencemodes.rigorexists to prevent. A missing bootstrap is invisible to a static read — the config block simply does not render — so verify it by running.
workflow (per .claude/docs/workflow-modes.md). The tier governs
which absent documents count as gaps (step 3) — below full, optional docs are
not flagged.
test cases passed, vs 3 / 13 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.