scope-check

To detect scope creep, compare current code and git history against baseline sprint documents to enumerate unplanned additions, removals, and TODO-driven expansions, yielding a net scope change percentage and bloat score.

Quantify unplanned feature additions by scanning repository files and TODO markers against original design documents, producing an itemized additions report and a canonical PASS, CONCERNS, or FAIL verdict for the sprint.

Yes, you can assess sprint risk by analyzing in-progress work against the baseline plan, which generates a risk assessment and prioritized cut or defer recommendations for producers and leads to manage scope bloat.

Yes, baseline design documents are required to analyze feature scope changes. The analysis locates original scope documents in design directories and aborts the scope review if no baseline is found to compare against.

Calculate net scope change percentage by attributing implemented and in-progress items from current code and git history against the milestone plan, enumerating additions and removals to compute the overall bloat score.

If no original scope document exists, the scope creep analysis aborts immediately because baseline discovery fails. Locating baseline design or sprint documents is a prerequisite to comparing current implementation against the plan.