scope-guard

# scope-guard ## Purpose Passive scope monitor. Reads the original task plan, inspects current git diff to see what files have changed, and compares them against the planned scope. Flags any unplanned additions as scope creep with specific file-level detail. ## Called By (inbound) - `cook` (L1): Phase 6.6 scope drift detection when files touched > planned - `team` (L1): after each parallel workstream completes, before merge - `rescue` (L1): during safeguard phase to detect unplanned changes - `plan` (L2): optional scope validation after plan acceptance ## Calls (outbound) None — pure L3 monitoring utility. ## Executable Instructions ### Step 1: Load Plan Read the original task/plan from one of these sources (check in order): 1. TodoWrite task list — read active todos as the planned scope 2. `.rune/progress.md` — use `Read` on `D:\Project\.rune\progress.md` (or equivalent path) 3. If neither exists, ask the calling skill to provide the plan as a text description Extract from the plan: - List of files/directories expected to be changed - List of features/tasks planned - Any explicitly out-of-scope items mentioned ### Step 2: Assess Current Work Run `Bash` with git diff to see what has actually changed: ```bash git diff --stat HEAD ``` Also check staged changes: ```bash git diff --stat --cached ``` Parse the output to extract the list of changed files. ### Step 3: Compare For each changed file, determine if it is: - **IN_SCOPE**: file matches a planned file/di...