scope-check

Name: scope-check
Availability: InStock
Author: polsegu

Compare current implementation and active work against original scope plans.

Updated Apr 10, 2026

Search Tags:#git #project management #scope creep #risk assessment #sprint #scope-check

Ready to run

npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill scope-check-polsegu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/scope-check
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill scope-check-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and quantifies scope creep by comparing the current implementation and in-progress work against the original feature, sprint, or milestone plan so teams can make data-driven trimming and escalation decisions.

Core Features & Use Cases

Baseline discovery: Locates original scope documents in design and production directories and aborts if no baseline is found.
Current-state analysis: Scans code, git history, and TODO/FIXME markers to enumerate implemented and in-progress items.
Comparison, scoring, and action: Produces an itemized additions/removals report, a bloat score, a canonical PASS/CONCERNS/FAIL verdict, risk assessment, and prioritized cut/defer recommendations for producers and leads.

Quick Start

Run a scope review for the target feature or sprint by invoking the scope-check skill with the feature name or sprint identifier, for example: scope-check player-authentication.

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 in a sprint using git history?▼

To detect scope creep, compare current code and git history against baseline sprint documents to enumerate unplanned additions, removals, and TODO-driven expansions, yielding a net scope change percentage and bloat score.

What is the best way to quantify unplanned feature additions during development?▼

Quantify unplanned feature additions by scanning repository files and TODO markers against original design documents, producing an itemized additions report and a canonical PASS, CONCERNS, or FAIL verdict for the sprint.

Can I assess sprint risk and get cut recommendations for scope bloat?▼

Yes, you can assess sprint risk by analyzing in-progress work against the baseline plan, which generates a risk assessment and prioritized cut or defer recommendations for producers and leads to manage scope bloat.

Do I need baseline design documents to analyze a feature for scope changes?▼

Yes, baseline design documents are required to analyze feature scope changes. The analysis locates original scope documents in design directories and aborts the scope review if no baseline is found to compare against.

How do I calculate net scope change percentage for a milestone plan?▼

Calculate net scope change percentage by attributing implemented and in-progress items from current code and git history against the milestone plan, enumerating additions and removals to compute the overall bloat score.

What happens if no original scope document exists when checking for scope creep?▼

If no original scope document exists, the scope creep analysis aborts immediately because baseline discovery fails. Locating baseline design or sprint documents is a prerequisite to comparing current implementation against the plan.