scope-check

Scope creep in a software sprint is detected by comparing original planned scope documents against the current codebase and git history. This generates a bloat score and risk assessment to identify unplanned work that threatens project timelines.

Scope verification for game development features works by automatically retrieving baseline design docs and scanning the codebase to catalog implemented work. It then generates a structured report listing unplanned additions and dropped items.

The best way to quantify unplanned feature additions is by comparing baseline scope documents against current implementation artifacts. This calculates a quantitative bloat score and schedule risk ratings to prioritize cuts or deferrals.

Scope creep analysis requires baseline scope documents like design docs, sprint plans, or milestone roadmaps to function properly. Without these original planned scope documents, the Skill cannot quantitatively compare against the current implementation state.

You can analyze git commit history alongside the codebase and TODO comments to catalog all implemented and in-progress work. This current state analysis identifies both unplanned additions and dropped scope items from the original plan.

To get recommendations for cutting features and staying on schedule, analyze the generated scope report containing risk ratings and bloat scores. This report provides prioritized recommendations for cutting, deferring, or keeping unplanned scope additions.