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.
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.
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.
Scope Guard is a passive L3 monitoring utility that reads a task plan, inspects git diff, and classifies scope drift into 4 tiers (ON_TRACK through OUT_OF_CONTROL). No scripts bundled — pure instruction-based skill for orchestration frameworks. Well-structured with clear steps, edge cases documented in Sharp Edges, and explicit constraints. No security concerns; skill is advisory-only and does not modify code or block commits.
Clean skill with no security issues. Part of the Rune orchestration ecosystem (not standalone). Quality is good but would benefit from example output and more portable path handling. Usefulness is moderate — scope creep detection is valuable but this only works within the Rune framework context.
