project-stage-detect

project-stage-detect is a skill for Claude Code from cenconq25/claude-code-app-studio. It costs 65 tokens per session (1,762 once invoked), scanned A, original, MIT.

A read-only project audit that identifies whether work is at the concept, design, architecture, sprint, beta, or live-operations stage. It also lists missing project documents and suggests the next workflow.

In plain words
What is it for?
Use it when joining a project, returning after a break, or asking what stage the project is in.
Why use it?
It helps a team understand the current state of an unfamiliar or long-running project without manually inspecting every document.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Good fit Use it when joining a project, returning after a break, or asking what stage the project is in.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cenconq25/claude-code-app-studio/project-stage-detect
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add cenconq25/claude-code-app-studio --skill project-stage-detect
Clone the repo
git clone --depth 1 https://github.com/cenconq25/claude-code-app-studio

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for project-stage-detect

README.md
[![agentmods](https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/project-stage-detect/github.svg)](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/project-stage-detect)
Your own site
<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/project-stage-detect"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/project-stage-detect/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for project-stage-detect

Your own site · 80×15
<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/project-stage-detect"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/project-stage-detect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,762 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.01762
Opus 5 $0.00032 $0.00881
Sonnet 5 $0.00013 $0.00352
Haiku 4.5 $0.00006 $0.00176

Measured 5d ago against content hash 5b4450811558, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

project-stage-detect scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/project-stage-detect/SKILL.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Stage Detection

Read-only. This skill never writes a file — it inspects what is on disk and produces a stage verdict plus a gap list. The user runs follow-up skills based on the recommendation.


Purpose / When to Run

Run when:

  • A new collaborator joins the project
  • The user types "where are we", "what stage", or "audit"
  • After a long break to re-orient before picking up work
  • Before running /adopt, which goes deeper into format compliance

Distinct from /adopt: this skill checks what exists; /adopt checks whether what exists is compatible with the template's other skills.

Inputs

  • The entire repo on disk — globs and reads only

Outputs

  • A printed report. No files written.

Phase 1: Inventory the Artifacts

Run these checks silently first. Build a fact table.

1a: Concept

  • design/concept.md exists?
  • Does it contain at least the eight sections from /brainstorm's template? Grep for headings: One-liner, Target User, Core Promise, MVP Scope, Primary Metric, Tone, Monetization Stance, Riskiest Assumption.

1b: Framework setup

  • Read .claude/docs/technical-preferences.md. Is the Framework field still [TO BE CONFIGURED]?
  • Glob docs/framework-reference/*/VERSION.md — is a framework reference populated?
  • Detect actual code: package.json (RN/JS), pubspec.yaml (Flutter), *.xcodeproj (iOS native), app/build.gradle (Android native).

1c: Design Bible

  • design/design-bible.md exists?
  • Does it list color, type, space, radius, elevation, motion tokens? Grep section headings.

1d: Systems / PRDs

  • Count design/prd/*.md.
  • design/systems-index.md exists?
  • For each PRD, grep for the eight required PRD sections. Count incomplete ones.

1e: UX

  • Count design/ux/*.md.
  • For each, check for: Screen Goal, User Flow, Screen Layout, States, Empty/Loading/Error, Accessibility, Platform Notes, Implementation Hooks.

1f: Architecture

  • docs/architecture/architecture.md exists?
  • Count docs/architecture/ADR-*.md.
  • For each ADR, grep for ## Status. Count Accepted vs Proposed.
  • docs/architecture/control-manifest.md exists?
  • docs/architecture/tr-registry.yaml exists?

Read the full file on GitHub · 193 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 193 lines · 65 tokens per session scan A 5b4450811558

Subscribe to this mod's changes

project-stage-detect is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 65 tokens to every session and 1,762 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens