scope-check

Name: scope-check
Availability: InStock
Author: scomofo

Compare baseline scope documents against codebase state to quantify scope creep.

Updated Mar 28, 2026

Search Tags:#scope creep #risk assessment #sprint review #engineering triage #plan vs execution #backlog control

Ready to run

npx skills add https://github.com/scomofo/dragon-forge --skill scope-check-scomofo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/scope-check
Command: npx skills add https://github.com/scomofo/dragon-forge --skill scope-check-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scope-check helps teams detect and quantify scope creep by comparing the original planned work against what is currently implemented or in progress.

Core Features & Use Cases

Baseline discovery: Finds the original plan for a feature, sprint, or milestone by reading the expected design or production documents.
Current-state inspection: Scans the codebase for related changes and looks for indicators like TODO/FIXME and active sprint plan updates.
Actionable comparison report: Produces additions, removals, a bloat score, risk assessment, and concrete recommendations (cut, defer, keep, and flag decisions).

Quick Start

Run scope-check for the relevant sprint or feature name (for example, scope-check sprint-04) to generate a scope creep report with a PASS/CONCERNS/FAIL verdict.

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 by comparing a sprint plan against the actual codebase?▼

Scope creep detection works by loading a baseline sprint plan or feature design document, scanning the codebase for related changes, and comparing the original plan against the current implemented state to quantify unplanned additions.

What is a scope creep risk assessment and when do I need it?▼

A scope creep risk assessment evaluates whether a team is adding unplanned deliverables without corresponding cuts or timeline changes during workflow reviews, producing a quantified comparison and concrete recommendations on what to cut, defer, keep, or flag.

How do I generate a scope creep report for a specific sprint?▼

Run the scope-check command for the relevant sprint or feature name, such as sprint-04. The tool inspects repository evidence including commit history and codebase scans, then produces a report with a bloat score, risk assessment, and a canonical PASS, CONCERNS, or FAIL verdict.

Can I use codebase evidence like TODO and FIXME markers to measure unplanned work?▼

Yes, current-state inspection scans the codebase for related changes and looks for indicators like TODO and FIXME markers alongside active sprint plan updates to measure unplanned work and calculate a bloat score against the original plan.

What is the best way to decide what features to cut, defer, or keep during engineering triage?▼

The best way to perform engineering triage is to compare the original planned work against the in-progress state to produce actionable recommendations, yielding concrete cut, defer, keep, and flag decisions based on a quantified risk assessment.

Does scope creep detection work without a baseline scope document?▼

No, baseline discovery is required because the tool must read the original expected design or production documents to establish the planned work, which is then compared against the current implemented state to identify and quantify deviations.