scope-check

Compare original plans to current implementations and generate scope deviation reports.

Updated Apr 25, 2026

Search Tags:#planning #scope creep #reporting #sprint #risk #change-management

Ready to run

npx skills add https://github.com/packetalien/cursor-game-studios --skill scope-check-packetalien

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/packetalien/cursor-game-studios/tree/main/.cursor/skills/scope-check
Command: npx skills add https://github.com/packetalien/cursor-game-studios --skill scope-check-packetalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scope creep is a common risk in project planning and development; this skill helps teams quantify deviations from the original plan and prioritize corrective actions.

Core Features & Use Cases

Detects differences between the original scope and current implementation across documents, commits, and tasks.
Computes bloat, additions, and removals, then offers concrete recommendations for cuts, deferrals, or keepers.
Applicable to feature sprints, milestones, and design updates to keep projects on track and aligned with objectives.

Quick Start

Compare the current sprint plan against the baseline to generate a scoped 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 and quantify scope creep in a sprint?▼

Detect and quantify scope creep by comparing the original plan against current implementation across documents and tasks. This process surfaces additions, removals, and net change, generating a concise report with a risk assessment to help prioritize corrective actions.

What is the best way to compare original sprint plans to current implementation?▼

The best way to compare original sprint plans to current implementation is to apply gate-like checks that compute bloat and deviations. This yields a scoped change report detailing additions, removals, and overall net change to keep projects aligned with objectives.

Can I generate a risk assessment for design milestones and feature scope changes?▼

Yes, you can generate a risk assessment for design milestones and feature scope changes. By comparing the baseline to the current state, the assessment quantifies deviations and recommends concrete actions such as cuts, deferrals, or keepers to mitigate risk.

How do I get recommendations for cuts or deferrals when project scope changes?▼

Get recommendations for cuts or deferrals by analyzing the net change between the baseline plan and current tasks. The analysis evaluates bloat and scope deviations to offer concrete corrective actions, prioritizing what to keep, cut, or defer to stay on track.

Does scope change management work for both feature sprints and design updates?▼

Yes, scope change management works for both feature sprints and design updates. It detects differences between the original scope and current implementation, computing bloat and removals to keep milestones on track and aligned with project objectives.

Why does my sprint planning need gate-like checks for scope deviations?▼

Sprint planning needs gate-like checks for scope deviations to prevent uncontrolled additions from derailing the timeline. Enforcing these checks computes bloat and net change, producing a risk report that recommends deferrals or cuts to maintain project alignment.