scope-guard

Compare git changes against a task plan to classify scope creep.

82|23|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Rune-kit/rune --skill scope-guard-rune-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-guard
Source: https://github.com/Rune-kit/rune/tree/main/skills/scope-guard
Command: npx skills add https://github.com/Rune-kit/rune --skill scope-guard-rune-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically monitors your project's progress against the original plan, detecting and flagging any changes that deviate from the defined scope to prevent uncontrolled expansion of work.

Core Features & Use Cases

  • Automated Scope Monitoring: Compares current git changes against the project plan.
  • Creep Detection: Identifies and categorizes out-of-scope files and changes.
  • Use Case: As you implement new features, this skill passively checks if you're accidentally modifying files or adding functionality not originally planned, alerting you to potential scope creep before it becomes a major issue.

Quick Start

Let the scope-guard skill analyze your current git changes against the project plan.

Frequently Asked Questions about scope-guard

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

FAQPage Schema
How do I detect scope creep in my git workflow?

Scope creep detection in your git workflow is handled by comparing current git diff file paths against an original task plan, categorizing changes as IN_SCOPE, MINOR CREEP, or SIGNIFICANT CREEP to prevent uncontrolled work expansion.

What is automated scope monitoring for software development?

Automated scope monitoring is the process of comparing current git changes against a defined project scope list to identify out-of-scope file modifications, alerting you to potential project deviation before it becomes a major issue.

How do I monitor project compliance against an original task plan?

You monitor project compliance by parsing git diff output and comparing the modified file paths against a defined scope list from your original task plan to ensure implementation stays within approved boundaries.

Does scope monitoring work with uncommitted git changes?

Scope monitoring works by parsing git diff output, meaning it evaluates current file changes regardless of commit status, as long as the changes are visible in the diff output against the defined scope list.

How does it classify changes as minor or significant creep?

It classifies changes as minor or significant creep by parsing git diff output and comparing the modified file paths against your defined scope list to measure the deviation from the original task plan.

What do I need to set up before checking for scope creep?

You need an active git repository with current changes and a defined scope list from your original task plan to compare file paths against for accurate scope creep detection.