scope-check

Compare original project plans against current development to quantify scope creep.

Updated Apr 8, 2026

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

Ready to run

npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill scope-check-hechaoyannet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/scope-check
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill scope-check-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scope creep detection and mitigation for project work.

Core Features & Use Cases

Compare original baselines against current work to surface deviations in scope and schedule.
Quantify additions, removals, and changes in effort across features, sprints, and milestones.
Produce actionable recommendations to prune scope or re-scope the project.

Quick Start

Run the scope-check on a project baseline to generate the comparison 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 my project sprints?▼

Detect scope creep by comparing your original project baseline against current development to quantify feature additions, removals, and schedule impacts. This generates a structured report with a bloat score to surface deviations across sprints.

What is the best way to quantify additions and removals in project scope?▼

Quantify additions and removals in project scope by comparing the original plan with current development milestones. This produces a structured report showing effort changes, a bloat score, and risk assessment to guide re-scoping.

How do I assess risk and timeline impacts from design changes?▼

Assess risk and timeline impacts from design changes by applying scope comparison to feature sprints and milestones. This surfaces deviations and produces a structured report with risk assessment and recommended actions for pruning.

Can I use scope analysis for feature milestone planning?▼

Yes, you can use scope analysis for feature milestone planning by comparing original baselines against current work. This surfaces scope and schedule deviations, generating actionable recommendations to prune or re-scope the project.

How do I generate a bloat score to evaluate project scope creep?▼

Generate a bloat score to evaluate project scope creep by comparing your original plan with current development. The resulting structured report quantifies additions, removals, and timeline impacts to recommend actions for pruning scope.

When do I need to re-scope my project?▼

You need to re-scope your project when scope comparison between the original baseline and current development surfaces significant additions and timeline impacts. The resulting report provides a bloat score and risk assessment to guide pruning actions.