scope-check
Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts.
npx skills add majiayu000/claude-skill-registry --skill scope-check-donchitos-claude-code-game-stu --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
When this skill is invoked: 1. **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/` 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 - Check for TODO comments that indicate unfinished scope additions 3. **Compare original vs current scope**: ```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] ### 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 - O
- Rules
What does the scope-check skill do?
Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill scope-check-donchitos-claude-code-game-stu --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.