A read-only review of whether a sprint or feature has grown beyond its original plan. A sprint is a short, fixed work period; scope is the work included in it.

Use it during a sprint, when considering a new story, or when a sprint is at risk. It compares the original plan with current stories, updates, and available git history.

It exposes scope creep—the gradual addition of work that can make a team miss its deadline or feel overloaded. It also recommends what to cut.

scope-check — Skill for Claude Code by cenconq25

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 scope-check

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/scope-check/github.svg)](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/scope-check)

Your own site

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/scope-check"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/scope-check/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/scope-check"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/scope-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,689 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.

Model	Per session	Once invoked
Fable 5.1	$0.00054	$0.01689
Opus 5.5	$0.00022	$0.00676
Sonnet 5.5	$0.00011	$0.00338
Haiku 4.5	$0.00005	$0.00169

Measured 1mo ago against content hash a1c656f7febb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

scope-check 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 1mo 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/scope-check/SKILL.md · 182 lines

How it starts

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

Scope Check

Sprints accumulate. A story added Tuesday because "it's quick" plus another Wednesday becomes Friday's overrun. This skill measures the drift from the original plan and surfaces a recommendation.

Read-only. Outputs a snapshot + cut recommendations.

Purpose / When to Run

Run when:

The team feels overloaded mid-sprint
A new story is being considered for an in-flight sprint
Sprint status shows "At risk" and the cause is unclear
A PM wants to confirm a feature has not silently expanded

Distinct from /sprint-status (current state) — this skill compares planned vs. actual scope.

Inputs

Mode: sprint (compare current sprint to its initial plan) or feature <slug> (compare an epic to its initial scope)
The relevant sprint plan or epic file
Mid-Sprint Update sections (added by /sprint-plan update)
All current stories
The git history if available — but the skill does not require it

Outputs

Printed snapshot. No file writes.

Phase 1: Resolve Mode

If no argument: ask

Prompt: "Check sprint scope or feature scope?"
Options: Active sprint, Specific feature (free text — epic slug)

Phase 2: Establish Baseline

For sprint mode:

Read the active sprint plan
Extract the original Sprint Backlog table (the one written when the plan was first created, before any ## Mid-Sprint Update section)
Extract the original sprint goal and Success Looks Like

For feature mode:

Read the epic's EPIC.md
Extract the original Story Backlog (Section 13 if it was filled before stories were added; else infer from the original PRD's TR-IDs)
Extract the original scope from EPIC Section 8 (Out of Scope)

Phase 3: Establish Current

Walk the same backlog now:

For sprint mode: read the live story files for each story in the plan, plus any added via Mid-Sprint Updates
For feature mode: list all stories under production/epics/<slug>/story-*.md

For each story now in scope, classify:

In original plan — was there from day 1
Added — appears in a Mid-Sprint Update section, or post-dates the original plan's create date
Expanded — was in the plan but acceptance criteria have grown (count criteria; if the story file has more than the plan implied, mark as expanded)

Read the full file on GitHub · 182 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.

1mo ago First seen · 182 lines · 54 tokens per session scan A a1c656f7febb

Subscribe to this mod's changes

scope-check is a skill published in the GitHub repository cenconq25/claude-code-app-studio (42 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 1,689 once invoked, about $0.0002 per session on Opus 5.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.

Planning Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

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

recipe-create-meet-space

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

googleworkspace/cli · 18 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

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

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens