scope-check

Compare implemented work to sprint or feature plans to detect undeclared scope changes.

70|42|Updated Mar 27, 2026

Search Tags:#risk-assessment #feature-analysis #sprint-planning #git-history #design-docs #scope-creep

Ready to run

npx skills add https://github.com/tranhieutt/software_development_department --skill scope-check-tranhieutt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/scope-check
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill scope-check-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies unauthorized scope creep by comparing the current implementation with the original feature or sprint plan, so teams catch bloat before it derails delivery.

Core Features & Use Cases

Plan comparison: Pulls relevant design docs or sprint plans and enumerates the declared work items to define the baseline scope.
Implementation audit: Surveys code, git history, and TODO notes to outline the current deliverables and highlight additions or removals.
Artifacts: Generates a scope delta, addition tables, recommended cuts, and a verdict that helps producers decide whether to stay the course or replan this sprint.
Use Case: Run it mid-sprint when engineering reports new features so product leadership understands whether those additions are justified or if they must be deferred.

Quick Start

Run scope-check with the feature or sprint name to compare the current work against the original scope and get actionable guidance.

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 current implementation against the original sprint plan?▼

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.

What is the best way to audit git history for scope additions during a sprint?▼

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.

When do I need to run a scope delta analysis for feature delivery?▼

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.

Does scope creep detection work without existing design docs or milestone definitions?▼

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.

How do I quantify missing work items and unauthorized additions in a sprint review?▼

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.

Scope-check is not detecting baseline deviations, what are the limitations?▼

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.