New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Scope Creep Check

by Donchitos in Donchitos/Claude-Code-Game-Studios

Compares the current state of a feature, sprint or milestone with its original plan, flags added scope, quantifies the growth and recommends cuts.

MITAuto-check passedProduct & Project Management

Install Scope Creep Check

skills CLI
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill scope-check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Donchitos/Claude-Code-Game-Studios scope-check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/scope-check .claude/skills/scope-check && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
scope-check
GitHub stars
26k
Token cost
~1.6k tokens
SKILL.md length
600 words
Files
1
Skills in repo
73
Repo updated
First seen
Licence
MIT

At a glance

Compares the current state of a feature, sprint or milestone with its original plan, flags added scope, quantifies the growth and recommends cuts.

  • Works in 5 steps: Find the Original Plan → Read the Current State → Compare Original vs Current Scope → …
  • Checking whether a sprint has grown beyond what was planned
  • SKILL.md covers Phase 1: Find the Original Plan, Phase 2: Read the Current State, Phase 3: Compare Original vs… and Phase 4: Verdict, plus 1 more section
  • Calls git

What it does

This read-only skill needs a baseline to compare against, so it first finds the planning document: a design file for a feature, a sprint plan for a sprint number, or a milestone file for a milestone. If the document does not exist, it reports the missing file and stops. It then reads the current state from related source files, git history since the start date, TODO and FIXME comments and the active sprint plan.

The comparison report ends in a verdict based on net scope change: up to 10% is PASS, 10 to 25% is CONCERNS, 25 to 50% is FAIL for significant creep, and above 50% is FAIL for out of control. When the baseline lists no scope items or the current state cannot be determined, it returns NOT ASSESSED instead of a percentage.

When your agent uses it

  • Checking whether a sprint has grown beyond what was planned
  • Measuring how far a feature has drifted from its design document
  • Deciding which additions to cut when a milestone is slipping

Example prompts

  • “Run a scope check on sprint-3.”
  • “Has the crafting system grown past its GDD. Compare and recommend cuts.”
  • “Check scope creep for the beta milestone.”

Requirements

  • A baseline plan document such as a GDD, sprint plan or milestone file
  • git history for the work being checked
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Bash(git log *)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Find the Original Plan
  2. Read the Current State
  3. Compare Original vs Current Scope
  4. Verdict
  5. Next Steps

What it can do on your machine

Read from SKILL.md and the folder at commit b21fa0f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Bash(git log *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Scope Creep Check loads about 1.6k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 600 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Donchitos/Claude-Code-Game-Studios at commit b21fa0f, republished under its MIT licence (© Donchitos). 600 words, ~1,602 tokens.

Download SKILL.mdSave it as .claude/skills/scope-check/SKILL.md (or your agent's skills folder).
name
scope-check
description
Scope creep check — current scope versus the original plan. Flags additions, quantifies bloat, recommends cuts. 'Any scope creep?'
allowed-tools
Read, Glob, Grep, Bash(git log *)
argument-hint
[feature-name or sprint-N]
user-invocable
true
model
haiku

Scope Check

This skill is read-only — it reports findings but writes no files.

Compares original planned scope against current state to detect, quantify, and triage scope creep.

Argument: $ARGUMENTS — the whole string: a feature name (it may be several words), sprint number, or milestone name.

Phase 1: Find the Original Plan

Locate the baseline scope document for the given argument:

  • Feature name → read design/gdd/[feature].md or matching file in design/
  • Sprint number (e.g., sprint-3) → read production/sprints/sprint-003.md (the name /sprint-plan writes) or similar
  • Milestone → read production/milestones/[name].md

If the document is not found, report the missing file and stop. Do not proceed without a baseline to compare against.

Phase 2: Read the Current State

Check what has actually been implemented or is in progress:

  • Scan the codebase for files related to the feature/sprint
  • Read git log for commits related to this work (git log --oneline --since=[start-date])
  • Check for TODO/FIXME comments that indicate unfinished scope additions
  • Check active sprint plan if the feature is mid-sprint

Phase 3: Compare Original vs Current Scope

Produce the comparison report:

markdown
## Scope Check: [Feature/Sprint Name]
Generated: [Date]

### Original Scope
[List of items from the original plan]

### Current Scope
[List of items currently implemented or in progress]

> **If Phase 4 will return NOT ASSESSED, do not render the numeric block below.**
> Replace the counts and the Bloat Score with
> `[Baseline | Current state] unusable — see verdict` (whichever side could not
> be read) and give the reason. A rendered
> `Original items: 0 / Net scope change: 0%` one section above a NOT ASSESSED
> verdict re-creates the exact "0% reads as on track" hazard Phase 4 exists to
> kill, one phase earlier — and readers trust a number over a caveat.

### Scope Additions (not in original plan)
| Addition | Source | When | Justified? | Effort |
|----------|--------|------|------------|--------|
| [item] | [commit/person] | [date] | [Yes/No/Unclear] | [S/M/L] |

### Scope Removals (in original but dropped)
| Removed Item | Reason | Impact |
|-------------|--------|--------|
| [item] | [why removed] | [what's affected] |

### Bloat Score
- Original items: [N]
- Current items: [N]
- Items added: [N] (+[X]%)
- Items removed: [N]
- Net scope change: [+/-N] ([X]%)

### Risk Assessment
- **Schedule Risk**: [Low/Medium/High] — [explanation]
- **Quality Risk**: [Low/Medium/High] — [explanation]
- **Integration Risk**: [Low/Medium/High] — [explanation]

### Recommendations
1. **Cut**: [Items that should be removed to stay on schedule]
2. **Defer**: [Items that can move to a future sprint/version]
3. **Keep**: [Additions that are genuinely necessary]
4. **Flag**: [Items that need a decision from producer/creative-director]

Phase 4: Verdict

Assign a canonical verdict based on net scope change:

Net ChangeVerdictMeaning
≤10%PASSOn Track — within acceptable variance
10–25%CONCERNSMinor Creep — manageable with targeted cuts
25–50%FAILSignificant Creep — must cut or formally extend timeline
>50%FAILOut of Control — stop, re-plan, escalate to producer

Before applying that table, check that the percentage means something. Emit NOT ASSESSED instead — never a computed percentage — when any of:

  • The baseline document exists but enumerates no scope items (all headings, placeholders, or [TO BE CONFIGURED]). Phase 1 stops when the file is absent; this is the case where it is present and empty, and it is the more dangerous one, because zero items yields a 0% net change that renders as PASS — On Track. Nothing was compared. Nothing was on track.
  • The current state cannot be determined — no related source files, no commits in the window, nothing in progress to read. Comparing a real baseline against an unreadable present is not a 0% change, and not the −100% that zero current items computes — the table reads both as PASS.
  • The denominator would be zero for any other reason. A percentage computed from no baseline items is not a small number; it is not a number.

NOT ASSESSED outranks PASS (a comparison that never happened has not shown scope is on track) and ranks below CONCERNS and FAIL (measured creep is more actionable than an unmeasurable baseline).

Output the verdict prominently:

**Scope Verdict: [PASS / CONCERNS / NOT ASSESSED / FAIL]**
Net change: [+X%] — [On Track / Minor Creep / Significant Creep / Out of Control]
           [or: NOT ASSESSED — [which side could not be read, and why]]
Show full SKILL.md (185 more words)Show less

Phase 5: Next Steps

After presenting the report, offer concrete follow-up:

  • PASS → no action required. Suggest re-running before next milestone.
  • NOT ASSESSED → say which side was unreadable and what would fix it (populate the baseline document, or point the skill at where the work actually lives). Do not offer a re-run against the same inputs — it will produce the same non-answer.
  • CONCERNS → offer to identify the 2–3 additions with best cut ratio. Reference /sprint-plan update to formally re-scope.
  • FAIL → recommend escalating to producer. Reference /sprint-plan update for re-planning or /estimate to re-baseline timeline.

End every verdict except NOT ASSESSED with:

"Run /scope-check [name] again after cuts are made to verify the verdict improves."

(NOT ASSESSED ends with what would make it assessable, above — a re-run against the same inputs would repeat the non-answer.)

Rules
  • Scope creep is additions without corresponding cuts or timeline extensions
  • Not all additions are bad — some are discovered requirements. But they must be acknowledged and accounted for
  • When recommending cuts, prioritize preserving the core player experience over nice-to-haves
  • Always quantify scope changes — "it feels bigger" is not actionable, "+35% items" is

© Donchitos, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/scope-check of Donchitos/Claude-Code-Game-Studios.

Open the folder on GitHubat commit b21fa0f

Compare with similar skills

Scope Creep Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Scope Creep Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scope Creep Check this skillDonchitos/Claude-Code-Game-Studios26k—~1.6kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Project Status Artifactanthropics/claude-plugins-official38k—~5.1kAutomated safety check: PassApache-2.0
Project Planneraiskillstore/marketplace4301 repos~504Automated safety check: PassMIT
Ijfw Milestone SummaryFerroxLabs/ijfw212—~1.5kAutomated safety check: PassMIT
Project Ops SkillOpenLoaf/OpenLoaf108—~1.3kAutomated safety check: PassAGPL-3.0

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Project Status Artifact

    anthropics/claude-plugins-official

    Official

    Builds and publishes a tabbed status page for a project with several workstreams, kept current by refreshing the same private page.

    38k GitHub stars~5.1k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Project Planner

    aiskillstore/marketplace

    Detects stale project plans and suggests session commands. An agent skill from aiskillstore/marketplace.

    430 GitHub starsUsed in 1 repo~504 tokens
    Product & Project ManagementAuto-check passed

  • Ijfw Milestone Summary

    FerroxLabs/ijfw

    A skill your agent uses when the user asks for a milestone summary, milestone recap, or to summarize a milestone -- or runs /ijfw-milestone-summary.

    212 GitHub stars~1.5k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

  • Project Ops Skill

    OpenLoaf/OpenLoaf

    Triggered when the user wants to create, open, switch, move, delete, or rename OpenLoaf's "project" entity.

    108 GitHub stars~1.3k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed

  • GitHub Sync Helper

    OpenMinis/MinisSkills

    General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment.

    444 GitHub stars~2.8k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from Donchitos/Claude-Code-Game-Studios

All 73 skills in this repo

  • Game Asset Audit

    Donchitos/Claude-Code-Game-Studios

    Audits game assets against naming conventions, file size budgets and format standards, and finds orphaned assets and missing references.

    26k GitHub stars~2k tokensUpdated 9 days ago
    Auto-check passed

  • Game Asset Spec Writer

    Donchitos/Claude-Code-Game-Studios

    Writes per-asset visual specs and AI image-generation prompts for a game's characters, enemies and screens, driven by the GDD, art bible and an entity inventory.

    26k GitHub stars~5k tokensUpdated 9 days ago
    Auto-check passed

  • Game Balance Check

    Donchitos/Claude-Code-Game-Studios

    Checks game data and formulas for balance outliers, broken progression, degenerate strategies and economy problems, and answers 'could not run' when the data is missing.

    26k GitHub stars~2.2k tokensUpdated 9 days ago
    Auto-check passed

  • Structured Bug Reports

    Donchitos/Claude-Code-Game-Studios

    Turns a description into a structured bug report, or scans code for likely bugs, then verifies and closes reports through four modes.

    26k GitHub stars~2.5k tokensUpdated 9 days ago
    Auto-check: notes

  • Bug Triage

    Donchitos/Claude-Code-Game-Studios

    Reviews the open bug backlog, separates severity from priority, assigns fixes to sprints and reports systemic trends, writing a dated triage file.

    26k GitHub stars~2.3k tokensUpdated 9 days ago
    Auto-check passed

  • Changelog Generator for Games

    Donchitos/Claude-Code-Game-Studios

    Generates an internal or player-facing changelog from git commits and sprint data, filtering out framework maintenance commits so that only work on the game itself reaches release copy.

    26k GitHub stars~2.5k tokensUpdated 9 days ago
    Auto-check: notes

Works with

Categories

Questions about Scope Creep Check

What does Scope Creep Check do?

Compares the current state of a feature, sprint or milestone with its original plan, flags added scope, quantifies the growth and recommends cuts. This read-only skill needs a baseline to compare against, so it first finds the planning document: a design file for a feature, a sprint plan for a sprint number, or a milestone file for a milestone. If the document does not exist, it reports the missing file and stops.

When should I use Scope Creep Check?

Scope Creep Check fits situations like: checking whether a sprint has grown beyond what was planned; measuring how far a feature has drifted from its design document; deciding which additions to cut when a milestone is slipping.

How do I install Scope Creep Check in Claude Code?

Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill scope-check -a claude-code`. Or copy the skill folder (.claude/skills/scope-check in Donchitos/Claude-Code-Game-Studios) into .claude/skills/scope-check in your project. Claude Code loads it when a task matches its description.

How do I install Scope Creep Check in Codex?

Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill scope-check -a codex`. Or copy the skill folder (.claude/skills/scope-check in Donchitos/Claude-Code-Game-Studios) into .agents/skills/scope-check in your project. Codex loads it when a task matches its description.

Can I use Scope Creep Check in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Donchitos/Claude-Code-Game-Studios --skill scope-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scope-check, .gemini/skills/scope-check, .github/skills/scope-check and .opencode/skills/scope-check in your project.

What does Scope Creep Check need to run?

Going by SKILL.md and its folder, Scope Creep Check needs the command-line tools its instructions call (git). Our summary lists: A baseline plan document such as a GDD, sprint plan or milestone file; git history for the work being checked. Its frontmatter pre-approves these tools: Read, Glob, Grep, Bash(git log *).

Does Scope Creep Check access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Scope Creep Check safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Scope Creep Check use?

Scope Creep Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Scope Creep Check use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Scope Creep Check?

Skills that share tags, products or a category with Scope Creep Check: CCPM Project Management (automazeio/ccpm, 8.4k stars), Project Status Artifact (anthropics/claude-plugins-official, 38k stars), Project Planner (aiskillstore/marketplace, 430 stars) and Ijfw Milestone Summary (FerroxLabs/ijfw, 212 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scope Creep Check?

Donchitos (a GitHub user) maintains it in Donchitos/Claude-Code-Game-Studios, which has 25,871 GitHub stars. The repository holds 73 skills in this directory. The repository was last updated on September 29, 2026.

Source: Donchitos/Claude-Code-Game-Studios on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.