scope-check

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

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill scope-check-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/scope-check
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill scope-check-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature work and sprints often grow beyond their original plan without anyone noticing until deadlines slip. This Skill compares the original scope document against what has actually been built, quantifies the bloat, and recommends what to cut, defer, or keep. ## Core Features & Use Cases - Baseline Comparison: Locates the original plan (GDD feature doc, sprint plan, or milestone file) and diffs it against current code, git history, and TODO comments. - Quantified Bloat Score: Reports items added, removed, and net scope change as a percentage, with schedule, quality, and integration risk ratings. - Canonical Verdict: Assigns PASS, CONCERNS, or FAIL based on net change thresholds, plus concrete cut/defer/keep recommendations. - Use Case: Before a sprint review, run a scope check on sprint-3 to discover it grew 35% beyond plan, then use the recommendations to decide which additions to defer to the next milestone. ## 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.

Frequently Asked Questions about scope-check

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

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

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

How is scope creep quantified in a scope review?

Scope creep is measured as the percentage change between original planned items and current items. Net change of 10% or less passes, 10-25% raises concerns, and anything above 25% fails and requires cuts or a formal timeline extension.

What happens if the original plan document is missing?

The Skill reports the missing baseline file and stops without producing a comparison. A scope check requires an original plan document, such as a GDD feature file, sprint plan, or milestone file, to compare against.

Does the scope check modify any project files?

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

When should I escalate scope creep to a producer?

Escalate when the verdict is FAIL, meaning net scope change exceeds 25%. At that point the Skill recommends re-planning the sprint or re-baselining the timeline estimate rather than absorbing the additions silently.