skills.rest
frabcd
frabcdCOMMUNITY
Explore all skills by this author →
GitHub

scope-check

Detects and quantifies scope creep by comparing planned scope against current implementation.

13|Updated Jul 30, 2026
Search Tags:#project management#scope creep#risk assessment#sprint review#milestone tracking#backlog analysis#game production
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill scope-check-frabcd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/scope-check
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill scope-check-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature work and sprints quietly accumulate unplanned additions, and teams often lack an objective way to measure how far current scope has drifted from the original plan before schedules slip. ## Core Features & Use Cases - Baseline Comparison: Locates the original plan (GDD feature doc, sprint plan, or milestone file) and compares it against code, git history, and TODO markers to list additions and removals. - Quantified Bloat Score: Reports net scope change as a percentage and assigns a canonical verdict (PASS, CONCERNS, or FAIL) with schedule, quality, and integration risk ratings. - Actionable Recommendations: Suggests what to cut, defer, keep, or escalate, and links to sprint re-planning and re-estimation follow-ups. - Use Case: Before a milestone review, run a scope check on sprint-3 to discover the feature set grew 35%, then cut the two lowest-value additions to get back on track. ## Quick Start Ask the AI to run a scope check on a feature or sprint, for example: check whether sprint-3 has any scope creep against its original plan.

Frequently Asked Questions about scope-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check for scope creep in a sprint?▼

Run the scope check with the sprint identifier, such as sprint-3. It reads the original sprint plan from production/sprints, compares it against current code and git history, and reports additions, removals, and a net scope change percentage.

How is scope creep quantified in a scope review?▼

Scope creep is measured as net scope change: original item count versus current item count, expressed as a percentage. A change of 10% or less passes, 10-25% raises concerns, and anything above 25% fails and requires cuts or re-planning.

What inputs does a scope check need to work?▼

It needs a baseline planning document: a feature GDD in design/, a sprint plan in production/sprints/, or a milestone file in production/milestones/. If the baseline document is missing, the check stops and reports the missing file rather than guessing.

Does the scope check modify any project files?▼

No, the skill is read-only. It scans the codebase, git log, and planning documents to produce a report, but writes no files and makes no changes to the project.

What should I do when a scope check returns FAIL?▼

A FAIL verdict means scope grew more than 25%. Escalate to the producer, use sprint-plan update to formally re-scope, or run an estimate to re-baseline the timeline, then re-run the scope check to confirm improvement.

Related Skills

Explore More Product & Management Skills→
pixel-cellarpixel-cellar
277

scope-check

Compares implemented code and plans to report added scope items and pruning recommendations.

Official
Advanced
MichaelSolatiMichaelSolati

scope-check

Compare planned scope against git history and codebase to quantify scope creep.

Community
Intermediate
MichaelSolatiMichaelSolati

milestone-review

Generate milestone progress reviews with go/no-go recommendations for game development.

Community
Advanced
solace-illsolace-ill

sprint-plan

Aggregate milestone data, completed work, and team capacity into sprint plans.

Community
Advanced