scope-check
Skill1 starsChanged 8 months agoMITView on GitHub
Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts.
26 other projects use a version of this, 10 of them edited.
Adopted by
Most recently taken up by
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
- striderZA/OpenCodeGameStudiosedited, first seen Nov 4, 2026
- momentmaker/kaijutsutheir own version, first seen Nov 1, 2026
- sentimony/skillstheir own version, first seen Nov 1, 2026
- Donchitos/Claude-Code-Game-Studiosedited, first seen Oct 19, 2026
- venus2099/codex-game-studiosedited, first seen Oct 17, 2026
Used with
Projects with it also use asset-spec, create-control-manifest and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lilangMaxSkillasset-spec
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Also in 8 projects that use this
lilangMaxSkillcreate-control-manifest
After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).
Also in 8 projects that use this
- +2 more from lilangMax
Other versions26 projects use a version of this.
Word for word · 2
- CoralGame/Claude-Code-Game-Studios★ 19100% same
- Swih/godot-foundry★ 1100% same
Edited · 10
- Donchitos/Claude-Code-Game-Studios★ 27k23% same
- pixel-cellar/Claude-Code-Game-Studios★ 32411% same
- striderZA/OpenCodeGameStudios★ 11843% same
- tranhieutt/software_development_department★ 7168% same
- dawn840705/codex-code-studios★ 1743% same
- lilangMax/ClaudeCodeGameStudios★ 843% same
- hongyuanc/codex-game-studios★ 536% same
- dawn840705/claude-code-studios★ 143% same
- HunLuanZhiZhu/Game-Studios-Plugin★ 143% same
- venus2099/codex-game-studios★ 124% same
Wrote their own version · 14
- cenconq25/claude-code-app-studio★ 40same name
- dvdarkin/claude-skills★ 11same name
- CodePhobiia/claude-roblox-game-studio★ 9same name
- anotherben/claude-harness★ 7same name
- sentimony/skills★ 7same name
- timjrobinson/Claude-Code-Construction-Manager★ 4same name
- zebbern/termstack★ 4same name
- momentmaker/kaijutsu★ 3same name
- nacif-software/skills★ 2same name
- evgenii-studitskikh/Claude-Code-SaaS-Studio★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-decisionSkill
- asset-auditSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- design-reviewSkill
- design-systemSkill
- estimateSkill
- gate-checkSkill
- hotfixSkill
- launch-checklistSkill
- localizeSkill
- map-systemsSkill
- milestone-reviewSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- playtest-reportSkill
- project-stage-detectSkill
- prototypeSkill
- release-checklistSkill
- retrospectiveSkill
- reverse-documentSkill
- setup-engineSkill
- sprint-planSkill
- startSkill
- team-audioSkill
- team-combatSkill
- team-levelSkill
- team-narrativeSkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
When this skill is invoked:
- Very specific: line 13
If a feature name: read the design doc from design/gdd/
- Very specific: line 14
If a sprint number: read the sprint plan from production/sprints/
- Very specific: line 15
If a milestone: read the milestone definition from production/milestones/
- Distinctive: line 19
Read git log for commits related to this work
- Distinctive: line 20
Check for TODO comments that indicate unfinished scope additions
- Distinctive: line 71
Not all additions are bad — some are discovered requirements.
- Distinctive: line 72
When recommending cuts, prioritize preserving the core player experience over nice-to-haves
- Distinctive: line 73
Always quantify scope changes — "it feels bigger" is not actionable, "+35% items" is
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
When this skill is invoked:
- Read the original plan — Find the relevant document:
- If a feature name: read the design doc from
design/gdd/ - If a sprint number: read the sprint plan from
production/sprints/ - If a milestone: read the milestone definition from
production/milestones/
- If a feature name: read the design doc from
- 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
- Check for TODO comments that indicate unfinished scope additions
Compare original vs current scope:
## 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] ### Scope Additions (not in original plan) | Addition | Who Added | 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]- Output the scope check with a clear verdict:
- On Track: Scope within 10% of original
- Minor Creep: 10-25% scope increase — manageable with adjustments
- Significant Creep: 25-50% scope increase — need to cut or extend timeline
- Out of Control: >50% scope increase — stop and re-plan
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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

