scope-check

Detect scope creep by comparing current implementation against the original sprint plan to identify unauthorized additions. This process gathers design docs, scans git history for scope-related commits, and catalogs TODOs to quantify baseline deviations before launch.

Auditing git history for scope additions involves scanning commits to outline current deliverables and highlight additions or removals. This implementation audit compares the current state against baseline design docs to catch unauthorized feature bloat mid-sprint.

Run a scope delta analysis mid-sprint when engineering reports new features. It generates addition tables, recommended cuts, and a verdict so product leadership understands whether additions are justified or must be deferred to prevent delivery derailment.

Scope creep detection requires existing design docs, sprint plans, or milestone definitions to establish a baseline scope. Without these preparatory documents, the Skill cannot enumerate declared work items or compare the current implementation state against the original feature plan.

Quantify missing work items and unauthorized additions by pulling design docs to define the baseline scope, then surveying code and TODO notes to outline current deliverables. This generates a scope delta table highlighting additions and removals for sprint-level delivery reviews.

Baseline deviation detection is limited when design docs or sprint plans are missing, preventing the enumeration of declared work items. Additionally, if git history lacks clear scope-related commits or TODO notes are sparse, quantifying additions and removals accurately becomes difficult.