scope-check

Project scope creep is identified by comparing current implementation against baseline documentation like GDDs or sprint plans. This generates a Bloat Score and net scope change percentage to quantify feature bloat and assess project health.

Feature bloat in game design is tracked by performing diff-based impact assessments against your Game Design Documents. The skill triages unauthorized additions by categorizing milestone status from PASS to OUT OF CONTROL with actionable recommendations.

Scope creep recommendations are generated by analyzing your project with a specific feature name or sprint number. The skill outputs risk-adjusted recommendations that specifically advise whether to cut, defer, or keep features based on the evaluated project health.

Yes, scope creep analysis requires access to your design and production directories. The skill needs these directories to perform diff-based impact assessments and accurately compare current implementations against your defined baseline documentation.

A key limitation when analyzing unauthorized feature additions is the strict dependency on having defined baseline documentation like GDDs or sprint plans. Without these baselines, the tool cannot perform diff-based impact assessments or calculate a meaningful Bloat Score.