scope-check

Compare planned scope to current implementation and report scope creep.

Updated Mar 26, 2026

Search Tags:#backlog #scope #project-management #sprint-planning #risk-analysis #scope-creep

Ready to run

npx skills add https://github.com/LordKuper/agentic-game-studio --skill scope-check-lordkuper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/LordKuper/agentic-game-studio/tree/main/.claude/skills/scope-check
Command: npx skills add https://github.com/LordKuper/agentic-game-studio --skill scope-check-lordkuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts. Use when user says 'any scope creep', 'scope review', 'are we staying in scope'.

Core Features & Use Cases

Detect scope creep by comparing baseline plans to current implementation
Quantify changes and surface potential cuts or refinements
Use in sprint planning and backlog grooming to stay on target

Quick Start

Run scope-check on a feature or sprint to generate a scope-change report.

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 by comparing the original plan to current implementation?▼

Detect scope creep by scanning design docs, code changes, and plans against baseline documents to surface additions and bloats, generating a detailed report with original scope, current scope, and a bloat score.

What is scope creep analysis and when should I run a scope review during sprint planning?▼

Scope creep analysis identifies unplanned additions by comparing current implementation to the original planned scope. Run a scope review during sprint planning or backlog grooming to stay on target and catch bloat early.

How do I quantify bloat and identify potential cuts in a feature backlog?▼

Quantify bloat by comparing baseline plans to current implementation, which surfaces additions, removals, and a bloat score. The resulting report provides actionable recommendations for potential cuts and refinements.

Can I use scope-check to review milestones and feature backlogs without additional dependencies?▼

Yes, you can review milestones and feature backlogs without dependencies. The analysis reads baseline documents and current state directly, applying to sprint efforts and feature scopes to flag additions.

What is the best way to stay on track and prevent scope creep during backlog grooming?▼

The best way to stay on track is running a scope comparison that flags additions and quantifies bloat. Use the generated report during backlog grooming to target cuts, refine the sprint effort, and prevent scope creep.

Why does my feature scope keep growing and how do I surface additions not in the original plan?▼

Your feature scope grows from scope creep when current implementation adds unplanned items. Surface these additions by scanning code changes and design docs against the original baseline plan to generate a detailed change report.