scope-check

Compare current implementation against original plans to detect scope creep.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill scope-check-carlosq96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/scope-check
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill scope-check-carlosq96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps product teams identify unintended growth in features or sprint work by comparing the current implementation against the original planning documents, preventing schedule delays and wasted effort.

Core Features & Use Cases

  • Baseline Retrieval: Automatically locates the original design or sprint documentation for a given feature, sprint, or milestone.
  • Current State Analysis: Scans code, git history, and TODO/FIXME comments to capture what has actually been built.
  • Scope Comparison Report: Generates a detailed markdown report showing original items, current items, added and removed elements, a bloat score, risk assessment, and actionable recommendations.
  • Verdict & Next Steps: Provides a concise PASS/CONCERNS/FAIL verdict with suggested actions to cut, defer, or keep items.

Quick Start

Run the scope-check skill with the name of the feature or sprint you want to review.

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 by comparing current code against original sprint planning documents?

To detect scope creep, the skill automatically locates original design or sprint documentation, scans current code and git history, then generates a comparison report detailing added or removed elements and a bloat score.

Can I analyze git logs and markdown files to assess project risk without modifying the repository?

Yes, you can analyze git logs, scan code files, and read markdown documents to assess project risk completely safely, as the skill performs read-only operations without modifying your repository.

What is the best way to get a scope comparison report for a specific project milestone?

The best way to get a scope comparison report is to run the skill with the feature or milestone name, which retrieves the baseline plan, analyzes the current state, and outputs a markdown report with a PASS, CONCERNS, or FAIL verdict.

How does a scope comparison tool handle TODO and FIXME comments during a sprint review?

During a sprint review, the tool scans TODO and FIXME comments alongside git history and code files to capture what has actually been built, comparing it against the original plan to identify unintended feature growth.

Does this scope analysis require any special dependencies or environment setup to run?

No special dependencies are required, as the skill operates standalone by reading markdown documents and scanning code and git logs directly from your project's design or production directories.

What actionable recommendations does the scope comparison report provide for cutting project bloat?

The report provides actionable recommendations to cut, defer, or keep specific items, assigning a bloat score and risk assessment to help you decide next steps and keep the project on track.