Verified:GitHub

scope-check

Compare original plans against current code to detect scope creep.

Updated May 13, 2026

Search Tags:#scope creep #sprint planning #risk assessment #git history #project governance #requirements tracking #bloat score

Ready to run

npx skills add https://github.com/FrancisVarga/the-dream-machine --skill scope-check-francisvarga

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/scope-check
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill scope-check-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scope-check helps teams detect scope creep early by comparing what was originally planned to what is actually being implemented, so you can quantify bloat and make clear tradeoffs.

Core Features & Use Cases

Original-vs-Current comparison: Finds a baseline plan (feature GDD, sprint doc, or milestone) and contrasts it with current code and activity (including TODO/FIXMEs and relevant git history).
Actionable change reporting: Produces additions, removals, and a bloat score with a quantified net scope change.
Decision-ready verdict: Assigns PASS/CONCERNS/FAIL based on net scope change, plus specific next steps (cut, defer, keep, flag) and schedule/quality/integration risk.

Quick Start

Run /scope-check sprint-03 to generate a scope creep report comparing the sprint plan against what’s currently in the codebase.

Frequently Asked Questions about scope-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect scope creep during a sprint?▼

To detect scope creep during a sprint, compare your original baseline plan against current implementation by scanning repository git history and codebase evidence to quantify additions, removals, and a bloat score.

What is a bloat score in project governance?▼

A bloat score in project governance quantifies the net scope change by measuring the difference between originally planned features and actual current implementation activity, helping teams track requirements bloat.

How do I assess schedule and integration risks from mid-sprint changes?▼

Assess schedule and integration risks from mid-sprint changes by contrasting the baseline milestone document with current TODOs and git history to issue a PASS, CONCERNS, or FAIL verdict with recommended next steps.

Can I compare a feature specification against current git history automatically?▼

Yes, you can compare a feature specification against current git history by locating the baseline document, scanning the repository for implementation evidence, and generating a decision-ready verdict on whether the work is staying in scope.

What is the best way to decide what features to cut when requirements exceed the plan?▼

The best way to decide what features to cut when requirements exceed the plan is to quantify net scope change and review a generated PASS, CONCERNS, or FAIL verdict that provides specific next steps to cut, defer, keep, or flag items.