speckit-scope-creep

Scope creep detection from git history compares the current specification against its earliest committed version. It quantifies growth across requirements, acceptance criteria, tasks, and phases, attributing additions to specific commits to reveal how effort expanded since the baseline.

Scope creep analysis in product planning reviews is a read-only historical comparison of specification files. It measures how requirements, scenarios, and external integrations have expanded across sprints, computing a complexity score and timeline to classify creep severity.

Measuring specification growth uses git log to discover the baseline version of .specify/spec.md and compare it to the current state. It outputs growth metrics, additions by commit, and a computed complexity score to quantify the expansion of requirements and tasks.

Scope creep detection requires the .specify/spec.md file in the repository to function properly. It relies on this file for baseline discovery via git log, and optionally analyzes plan.md and tasks.md if they are present in the committed history.

Use threshold-based recommendations for scope creep severity during delivery milestone planning to decide whether to re-estimate, split the scope, or freeze new additions. It classifies creep severity when requirements and task items have materially expanded beyond the original baseline.