scope-check

To quantify scope creep, compare current feature scope against the original plan by reading design docs and scanning git history to surface additions and removals. This produces a structured report with a bloat score, risk assessment, and recommendations to identify drift and overruns.

Sprint analysis detects project scope drift by reading sprint plans from production directories and comparing them against current code and git history. It surfaces unapproved additions and removals, calculating a bloat score to enforce a structured scope report with risk assessment and recommendations.

Yes, generating a scope report for milestones requires access to design docs, production milestone plans, and git history. The analysis reads these sources to compare the original scope against the current state, producing a bloat score, risk assessment, and final verdict.

The best way to spot scope creep before overruns occur is to systematically compare current code and commit history against the original design doc. This surfaces undocumented additions and quantifies the drift using a bloat score, enabling early risk assessment and corrective recommendations.

Yes, you can assess risk and generate recommendations without manual tracking by invoking an automated scope check on a feature name or sprint number. It reads the original plan, scans git history and TODOs, and outputs a structured report with a bloat score and final verdict.