skills.rest
Donchitos
DonchitosCOMMUNITY
Explore all skills by this author →
GitHub

scope-check

Compare original plans with current implementation to quantify scope creep.

23.7k|3.4k|Updated Feb 12, 2026
Search Tags:#project management#scope creep#sprint planning#risk assessment#feature analysis#development tracking
One-click install
npx skills add https://github.com/Donchitos/Claude-Code-Game-Studios --skill scope-check-donchitos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/scope-check
Command: npx skills add https://github.com/Donchitos/Claude-Code-Game-Studios --skill scope-check-donchitos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps prevent project delays and budget overruns by identifying and quantifying scope creep, ensuring that development stays aligned with the original plan.

Core Features & Use Cases

  • Scope Analysis: Compares implemented features against original design documents or sprint plans.
  • Bloat Quantification: Identifies and quantifies added scope, removed scope, and net change.
  • Risk Assessment: Evaluates schedule, quality, and integration risks associated with scope changes.
  • Recommendation Generation: Suggests items to cut, defer, or keep based on project goals.
  • Use Case: After a sprint, run /scope-check sprint-3 to see if any new features were added without a corresponding adjustment to the timeline or removal of other features.

Quick Start

Run the scope-check skill for sprint 5.

Frequently Asked Questions about scope-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check for scope creep after a sprint?▼

Scope creep is identified by comparing implemented features against original sprint plans to detect additions, removals, and quantify net bloat. This analysis assesses schedule and quality risks to recommend actions for maintaining project vision.

What is the best way to quantify project bloat during development tracking?▼

Project bloat is quantified by comparing current implementation status against original design documents to identify added scope, removed scope, and the net change. This process evaluates schedule and integration risks associated with these deviations.

How does risk assessment work for unplanned feature analysis in sprint planning?▼

Risk assessment for feature analysis evaluates schedule, quality, and integration risks caused by unplanned scope changes. It compares current implementation status against the original plan to determine the impact of added features on project timelines.

Can I use this to recommend which features to cut or defer during project management?▼

Yes, scope analysis recommends specific items to cut, defer, or keep based on your project goals. It evaluates the risk profile of scope changes to generate actionable recommendations that help maintain the original project vision.

Do I need original design documents to assess schedule risks from scope changes?▼

Yes, you need original design documents or sprint plans to serve as the baseline for comparison. The tool compares these original plans against current implementation status to accurately identify scope additions and assess associated schedule risks.

Related Skills

Explore More Product & Management Skills→
LordKuperLordKuper

scope-check

Compare planned scope to current implementation and report scope creep.

Community
Intermediate
DavidsonGomesDavidsonGomes

evo-sprint-status

Summarize current sprint status and surface blockers and risks.

Community
Advanced
BrennonTWilliamsBrennonTWilliams
7

go-no-go

Evaluate software issue viability through adversarial pro and con agent debate.

Community
Advanced
solace-illsolace-ill

scope-check

Compare current project scope against the original plan to quantify scope creep.

Community
Intermediate