scope-check

Detect scope creep by comparing implemented work against an approved sprint or milestone plan. This analysis reviews repository files, git history, and active TODOs to identify unplanned additions and quantify schedule risks.

Auditing unplanned work in a milestone requires comparing current implementation against the original baseline document. The audit examines git history and active plans to recommend which unplanned items to cut, defer, keep, or escalate.

A discoverable baseline document is required to review scope creep. The analysis locates the relevant feature, sprint, or milestone planning document first to establish the approved scope before comparing current implementation.

Git history is used to find dropped commitments and unplanned additions during sprint planning. The scope comparison reviews repository file changes and TODOs to detect removals and quantify the schedule impact of the current work.

When a sprint accumulates extra systems, calculate the scope change and assess integration risks to determine what should be removed. This protects the core experience by recommending items to cut or defer from the active plan.

Scope review does not work without repository access. Examining related files, git history, TODOs, and active plans requires direct repository access to accurately compare current implementation against the baseline plan.