Compare baseline plans against current code and commits to quantify scope creep.
npx skills add https://github.com/easonlao/jiazi-game --skill scope-check-easonlao
Please help me install this Agent Skill. Skill: scope-check Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/scope-check Command: npx skills add https://github.com/easonlao/jiazi-game --skill scope-check-easonlao
Scope-check prevents projects from silently expanding by comparing the original planned scope to what is currently implemented or in progress, then quantifying additions and recommending specific triage actions.
Use it when you suspect scope creep (e.g., mid-sprint concerns, feature discussions, or “are we staying in scope” checks) and you need an evidence-based report rather than intuition.
Run /scope-check with the feature name or sprint number you want to evaluate and read the generated scope verdict and recommended cuts.
High-intent search queries and answers about installing and using this skill.
Scope creep is detected by comparing your original baseline plan against the current codebase and commit history to identify uncontrolled additions, dropped items, and bloat risk. This structured comparison generates a risk assessment and a decision-ready verdict.
Net scope change is quantified by scanning implemented code and commits, then calculating a bloat score against the original feature baseline. This process flags specific additions and removals to provide an evidence-based comparison report.
Automated triage recommendations are generated after comparing the baseline plan to current implementation, providing specific follow-up actions to cut, defer, keep, or escalate features based on schedule, quality, and integration risks.
Baseline comparison works by locating the original sprint or milestone document, scanning the current codebase for actual progress, and deriving a structured report. It outputs a PASS, CONCERNS, or FAIL verdict with actionable next steps.
Manual code analysis is not required because the process automatically scans code and commit history against the baseline document. It satisfies read-only execution requirements to locate the plan, derive the comparison, and output an evidence-based bloat risk report.
tranhieuttCompare implemented work to sprint or feature plans to detect undeclared scope changes.
nuoyanruoshuiCompare implemented work against feature, sprint, or milestone plans to quantify scope creep.
kay6198835Compares planned scope with current implementation to produce a bloat score and risk assessment.
WindXRanCompare planned baselines against current codebase state to detect scope creep.
