Scope Guard

What it does

Scope Guard compares the current git diff with an explicit task plan (TodoWrite, .rune/progress.md, or a supplied plan) to identify files changed that were not part of the original scope. It computes a drift percentage and classifies the result into four tiers (ON_TRACK, MINOR_DRIFT, SIGNIFICANT_DRIFT, OUT_OF_CONTROL), and emits a detailed markdown report with per-file reasoning and remediation suggestions.

When to use it

Use Scope Guard in automated workflows and orchestrators to detect scope creep before work continues: e.g., after a development step, before merging, or when an L1 orchestrator wants to ensure changes match the original plan. It is triggered when files changed exceed expectations or when an explicit scope check is requested.

What's included

• Scripts: none (has_scripts=false)
• References: none (has_references=false)
• Instructions: loads the plan, runs git diff --stat (including staged changes), classifies each changed file as IN_SCOPE or OUT_OF_SCOPE, computes drift_pct, and outputs a markdown Scope Report with recommendations.

Compatible agents

Designed for orchestration and monitoring layers (L1/L3) and integrates well with Claude Code and other agent-driven orchestrators that can call read/grep/glob tools.