scope-check

You can detect scope creep by comparing original sprint plans against current implementation using this Skill, which scans git history, repository files, and TODO markers to produce a structured report with bloat metrics and risk assessments.

Quantifying feature bloat involves comparing original milestone plans to production code, computing a bloat score, and returning a verdict of PASS, CONCERNS, or FAIL with actionable recommendations for cutting or deferring work.

Auditing a sprint requires reading the original plan document and scanning the codebase for related changes, which generates a report listing all feature additions and removals to highlight deviations from the baseline scope.

Yes, you can assess project risk during sprint reviews by analyzing git history and production documents, which yields a risk assessment verdict and actionable escalation steps for producers to manage scope deviations.

To perform a scope audit, you need access to repository files, git logs, and original sprint plans, which the Skill reads to validate the baseline and analyze the current state of your implementation.