rune-scope-guard

Detects scope creep by comparing git diff changes against the original task plan.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-scope-guard-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-scope-guard
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-scope-guard
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-scope-guard-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? During AI-assisted coding sessions, work often drifts beyond the original plan, introducing unplanned features, unrelated refactors, and extra dependencies. This Skill quantifies that drift so orchestrators and users can catch scope creep before it compounds. ## Core Features & Use Cases - Plan vs. Actual Comparison: Loads the planned scope from TodoWrite tasks or .rune/progress.md and compares it against git diff output (staged and unstaged). - Drift Quantification: Computes a drift percentage and classifies it into four tiers: ON_TRACK, MINOR_DRIFT, SIGNIFICANT_DRIFT, and OUT_OF_CONTROL, each with a defined action. - Smart Classification Rules: Treats test files, config side-effects, and lock files as in-scope natural dependencies while flagging unplanned features and unrelated refactors. - Use Case: An L1 orchestrator finishes a parallel workstream and invokes this Skill before merging; it reports 40% drift caused by an unplanned component and recommends reverting two files before continuing. ## Quick Start Ask the agent to run a scope check comparing current git changes against the original plan and report the drift percentage with recommendations.

Frequently Asked Questions about rune-scope-guard

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

FAQPage Schema
How do I detect scope creep in an AI coding session?

Run a scope check that loads the original plan from TodoWrite tasks or .rune/progress.md, then compares it against git diff --stat output. Each changed file is classified as in-scope or out-of-scope, and a drift percentage is computed with a recommended action.

How is scope drift percentage calculated?

Drift percentage equals out-of-scope files divided by total changed files, multiplied by 100. Under 10% is ON_TRACK, 10-25% is MINOR_DRIFT, 25-50% is SIGNIFICANT_DRIFT, and over 50% is OUT_OF_CONTROL.

Are test files and lock files counted as scope creep?

No. Test files for planned source files, config changes caused by planned features, and lock files like package-lock.json, yarn.lock, and Cargo.lock are always classified as in-scope natural dependencies.

What happens if no plan exists to compare against?

If neither TodoWrite tasks nor .rune/progress.md is available, the Skill asks the calling skill to provide the plan as text. It also falls back to file-count thresholds: 1-2 extra files is MINOR_DRIFT, 3-5 is SIGNIFICANT_DRIFT, and 6 or more is OUT_OF_CONTROL.

Does scope-guard automatically revert out-of-scope changes?

No. It is advisory only: it reports drift, lists out-of-scope files with reasons, and recommends actions such as pausing or reverting. Override and revert decisions belong to the calling orchestrator or the user.