scope-check

Detect scope creep and shrinkage by analyzing issue scope, acceptance criteria, and code diffs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/emanuelrechsteiner/FairSplit --skill scope-check-emanuelrechsteiner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/emanuelrechsteiner/FairSplit/tree/main/.claude/skills/scope-check
Command: npx skills add https://github.com/emanuelrechsteiner/FairSplit --skill scope-check-emanuelrechsteiner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill verifies that work remains within the planned scope and detects scope creep (unplanned additions) as well as scope shrinkage (dropped features). It supports per-issue and per-phase granularity to ensure alignment with the original plan.

Core Features & Use Cases

  • Scope verification by analyzing issue scope sections (IN SCOPE / OUT OF SCOPE) and acceptance criteria.
  • Per-issue and per-phase mode detection to tailor checks for the current workflow.
  • Diff analysis and change validation to flag unplanned work and potential scope creep.
  • Guidance for scope changes and governance to support remediation.

Quick Start

Run the scope-check skill on the current feature branch to verify it stays within the defined scope.

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's code diffs?

Detect scope creep by analyzing code diffs against original issue scope and acceptance criteria. The skill flags unplanned additions and dropped features during per-issue or per-phase checks to ensure alignment with the original plan.

What is scope shrinkage and how do I track dropped features during development?

Scope shrinkage occurs when originally planned features are dropped during implementation. Track it by verifying per-issue acceptance criteria against actual code changes to report misaligned work and maintain governance.

Can I check for scope deviations during phase-gate reviews?

Yes, you can run per-phase mode detection to verify scope alignment during phase-gate reviews. The skill tailors checks for the current workflow to catch unplanned work before advancing to the next project phase.

What's the best way to enforce governance for change requests in issue tracking?

Enforce governance by applying structured guidance for change requests and remediation workflows during issue tracking. The skill identifies deviations and enforces governance rules to manage scope changes effectively.

How do I validate that my feature branch stays within the defined IN SCOPE and OUT OF SCOPE boundaries?

Validate feature branch scope by analyzing issue scope sections and acceptance criteria against code diffs. Run the check on the current branch to flag unplanned work and confirm it stays within defined boundaries.

When should I not rely on automated diff analysis for change management?

Automated diff analysis for change management may be limited when acceptance criteria are poorly defined or missing. The approach requires clear IN SCOPE and OUT OF SCOPE sections to effectively detect deviations and guide remediation.