scope-check

To detect scope creep, you can analyze project scope by comparing original plans against current implementation. This involves reading design docs, sprint plans, and commit history to surface scope changes and identify drift. The output is a structured report detailing additions, removals, and risks.

Tracking scope changes across sprints involves anchoring the original plan from production sprints or milestones and scanning code changes, git logs, and TODO markers. This surfaces drift to keep sprints on track and produces a formal report with a bloat score and risk assessment.

Yes, you can generate a scope creep report for a specific feature by reading the original plan from design docs and inspecting the current state via commit history. It produces a structured report including original scope, current scope, additions, removals, and actionable recommendations.

Scope analysis relies on reading existing design docs, sprint plans, or milestones to anchor the original scope. Without these predefined project management structures to establish a baseline, comparing against the current implementation to identify creep is not possible.

To assess bloat and risks when project scope drifts, compare the original plan to current implementation by scanning git logs and code changes. The analysis produces a structured report that includes a bloat score, risk assessment, and actionable recommendations to justify changes.