scope-check

Compare planned baselines against current codebase state to detect scope creep.

Updated Apr 4, 2026

Search Tags:#project planning #scope creep #risk assessment #sprint review #engineering triage #bloat quantification

Ready to run

npx skills add https://github.com/WindXRan/y3td --skill scope-check-windxran

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scope-check helps teams stop features from silently growing by comparing what was planned against what has actually shipped or is in progress.

Core Features & Use Cases

Original vs Current Comparison: Reads a baseline plan (feature, sprint, or milestone) and scans the current state to find implemented, in-progress, and still-pending work.
Quantified Change Reporting: Produces additions/removals tables and calculates bloat metrics like percentage change and net scope impact.
Actionable Verdict & Next Steps: Assigns PASS/CONCERNS/FAIL based on net change and recommends cuts, deferments, and escalation when needed.

Quick Start

Run /scope-check sprint-03 to generate a scope creep report for that sprint.

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 during a sprint review?▼

To detect scope creep during a sprint review, compare your original planned baseline against the current implemented state. This process scans the codebase for in-progress work and unfinished TODO items, identifying silent feature expansion beyond the baseline plan.

What is the best way to quantify bloat in project planning?▼

Quantify bloat in project planning by performing a structured comparison between the baseline plan and current production state. This calculates percentage change metrics and net scope impact, producing additions and removals tables to measure feature growth accurately.

How does baseline comparison work for engineering triage?▼

Baseline comparison for engineering triage works by performing read-only baseline lookups, scanning the codebase, and correlating git-log history. It identifies implemented and pending work to assess risk, yielding a structured comparison of additions and removals.

Can I assess risk and get a verdict on expanding milestone scope?▼

Yes, you can assess risk for expanding milestone scope by evaluating net change against the original plan. The assessment assigns a PASS, CONCERNS, or FAIL verdict, recommending cuts, deferments, or escalation when additions and unfinished items expand work beyond limits.

Do I need any dependencies to run a scope creep analysis?▼

No dependencies are required to run a scope creep analysis. The process performs read-only baseline lookups and git-log correlation directly within your existing environment to generate structured comparison reports without external components.