### Scope Check
Works with
description: "Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts. Use when user says 'any scope cr
argument-hint: "[feature-name or sprint-N]"
allowed-tools: Read, Glob, Grep, Bash
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionscope-checkExecute the skills CLI command in your project's root directory to begin installation:
Fetches scope-check from Donchitos/Claude-Code-Game-Studios and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate scope-check. Access via /scope-check in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Use skill to generate boilerplate code, refactor legacy code, and write tests faster
Example
Generate React component with TypeScript types, styled-components, and comprehensive test suite in minutes
Reduce development time by 40-60% for repetitive coding tasks
Systematically review code for bugs, security issues, and style violations
Example
Analyze pull requests for common anti-patterns, suggest performance improvements, flag security vulnerabilities
Catch 70%+ of code issues before human review, improve code quality
Trace errors through stack traces and identify root causes faster
Example
Analyze error logs, suggest probable causes, recommend fixes with code examples
0
total installs
0
this week
10.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
10.7K
stars
| name | scope-check |
| description | "Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts. Use when user says 'any scope creep', 'scope review', 'are we staying in scope'." |
| argument-hint | "[feature-name or sprint-N]" |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Bash |
| model | haiku |
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[0] — feature name, sprint number, or milestone name.
Locate the baseline scope document for the given argument:
design/gdd/[feature].md or matching file in design/sprint-3) → read production/sprints/sprint-03.md or similarproduction/milestones/[name].mdIf the document is not found, report the missing file and stop. Do not proceed without a baseline to compare against.
Check what has actually been implemented or is in progress:
git log --oneline --since=[start-date])Produce the comparison report:
## 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 | 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]
Assign a canonical verdict based on net scope change:
| Net Change | Verdict | Meaning |
|---|---|---|
| ≤10% | PASS | On Track — within acceptable variance |
| 10–25% | CONCERNS | Minor Creep — manageable with targeted cuts |
| 25–50% | FAIL | Significant Creep — must cut or formally extend timeline |
| >50% | FAIL | Out of Control — stop, re-plan, escalate to producer |
Output the verdict prominently:
**Scope Verdict: [PASS / CONCERNS / FAIL]**
Net change: [+X%] — [On Track / Minor Creep / Significant Creep / Out of Control]
After presenting the report, offer concrete follow-up:
/sprint-plan update to formally re-scope./sprint-plan update for re-planning or /estimate to re-baseline timeline.Always end with:
"Run
/scope-check [name]again after cuts are made to verify the verdict improves."
Cut debugging time by 30-50%, especially for unfamiliar codebases
Get explanations, examples, and best practices for unfamiliar frameworks
Example
Understand Next.js app router, learn Rust ownership, grasp Kubernetes concepts with practical examples
Accelerate learning curve by 2-3x, reduce onboarding time for new tech stacks
Prerequisites
Time Estimate
15-30 minutes to install and see first useful output
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use coding skills for boilerplate generation, code reviews, refactoring legacy code, writing tests, learning new frameworks, and debugging non-critical issues. Best for repetitive tasks where errors are easy to catch.
✗ Avoid when
Avoid for production security features (auth, encryption, payment processing), complex business logic requiring deep domain knowledge, performance-critical algorithms, or when learning fundamentals is more valuable than speed.
JuliusBrussee/caveman
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
vercel-labs/skills
scope-check fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in scope-check — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added scope-check from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
scope-check fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in scope-check — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for scope-check matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for scope-check matched our evaluation — installs cleanly and behaves as described in the markdown.
scope-check fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for scope-check matched our evaluation — installs cleanly and behaves as described in the markdown.
scope-check reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 43