skills.rest
XGanQAQ
XGanQAQCOMMUNITY
Explore all skills by this author →
GitHub

scope-check

Compare planned scope documents against code and git history to quantify scope creep.

1|Updated May 5, 2026
Search Tags:#scope creep#roadmap#risk assessment#sprint review#git log#project triage
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill scope-check-xganqaq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/scope-check
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill scope-check-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scope creep silently expands a feature or sprint until delivery, quality, and budget are threatened, and teams end up with vague “it feels bigger” disagreements instead of quantified decisions.

Core Features & Use Cases

  • Find the baseline plan by locating the original scope document (by feature name, sprint number, or milestone) and halting if it cannot be found.
  • Assess the current state by scanning the codebase for related work, checking git history for relevant commits, and reviewing TODO/FIXME or active sprint plan indicators.
  • Compare and quantify differences by producing additions/removals tables, a bloat score (including net scope change), risk assessment, and a PASS/CONCERNS/FAIL verdict with recommended next steps.
  • Use Case: Before committing to a near-term release, run a scope review to determine whether newly proposed additions are still within the original plan’s variance and which items should be cut, deferred, or escalated.

Quick Start

Run /scope-check sprint-03 to generate a quantified scope creep report for that sprint and a clear PASS/CONCERNS/FAIL verdict.

Frequently Asked Questions about scope-check

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

FAQPage Schema
How do I quantify scope creep during a sprint review?▼

To quantify scope creep during a sprint review, compare your original planned scope document against current implemented work by scanning the codebase and git history to compute a bloat score and risk assessment.

What is the best way to measure project bloat from git history?▼

Measuring project bloat from git history involves scanning relevant commits and codebase changes against a baseline scope file, identifying TODO/FIXME indicators, and calculating net scope change to output a structured verdict.

Can I run a project triage if the original scope document is missing?▼

You cannot run a project triage if the original scope document is missing, because the assessment requires reading the baseline scope file to halt execution and prevent inaccurate feature comparisons.

How do I decide what features to cut before a milestone release?▼

To decide what features to cut before a milestone release, generate a quantified scope creep report with a PASS, CONCERNS, or FAIL verdict that provides actionable recommendations on which items to defer or escalate.

When do I need to perform a scope creep risk assessment?▼

You need to perform a scope creep risk assessment during mid-sprint reviews, pre-milestone planning, and post-change audits when additions or uncertainty threaten your project schedule and delivery quality.

Related Skills

Explore More Product & Management Skills→
cipherstashcipherstash
17

Validating Review Feedback

Validate code review feedback against the implementation plan to prevent scope creep.

Official
Intermediate
TraftGTraftG
33

gate-check

Validate phase-gate readiness and produce a PASS/CONCERNS/FAIL verdict.

Community
Advanced
Euraika-LabsEuraika-Labs
14

retrospective

Generate sprint or milestone retrospectives from plans, git commits, and outcomes.

Official
Intermediate
dnkrowdnkrow
1

scope-check

Compare planned scope against codebase and git evidence to detect scope creep.

Community
Intermediate