scope-check

Name: scope-check
Availability: InStock
Author: NuoYan

Compare implemented work against feature, sprint, or milestone plans to quantify scope creep.

47|12|Updated Jun 14, 2026

Search Tags:#project management #scope creep #sprint planning #milestone tracking #git analysis #scope review

Ready to run

npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill scope-check-nuoyanruoshui

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/scope-check
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill scope-check-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies unplanned additions, dropped commitments, and schedule risks by comparing current implementation against an approved feature, sprint, or milestone plan.

Core Features & Use Cases

Baseline Discovery: Locates the relevant feature, sprint, or milestone planning document before analysis.
Scope Comparison: Reviews implementation files, git history, TODOs, and active plans to identify additions and removals.
Quantified Recommendations: Calculates scope change, assesses schedule and integration risks, and recommends items to cut, defer, keep, or escalate.
Use Case: When a sprint has accumulated extra systems and polish work, use this Skill to determine whether the additions exceed the original plan and what should be removed to protect the core experience.

Quick Start

Use the scope-check skill to review scope creep for the specified feature, sprint, or milestone.

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 sprint plan?▼

Detect scope creep by comparing implemented work against an approved sprint or milestone plan. This analysis reviews repository files, git history, and active TODOs to identify unplanned additions and quantify schedule risks.

What is the best way to audit unplanned work in a milestone?▼

Auditing unplanned work in a milestone requires comparing current implementation against the original baseline document. The audit examines git history and active plans to recommend which unplanned items to cut, defer, keep, or escalate.

Do I need a baseline document to review scope creep?▼

A discoverable baseline document is required to review scope creep. The analysis locates the relevant feature, sprint, or milestone planning document first to establish the approved scope before comparing current implementation.

Can I use git history to find dropped commitments during sprint planning?▼

Git history is used to find dropped commitments and unplanned additions during sprint planning. The scope comparison reviews repository file changes and TODOs to detect removals and quantify the schedule impact of the current work.

What should I do when my game development sprint has accumulated extra systems?▼

When a sprint accumulates extra systems, calculate the scope change and assess integration risks to determine what should be removed. This protects the core experience by recommending items to cut or defer from the active plan.

Does scope review work without repository access?▼

Scope review does not work without repository access. Examining related files, git history, TODOs, and active plans requires direct repository access to accurately compare current implementation against the baseline plan.