From rune
Detects scope creep by comparing git diffs against original plan, quantifies drift percentage, classifies into ON_TRACK, MINOR_DRIFT, SIGNIFICANT_DRIFT, OUT_OF_CONTROL tiers.
npx claudepluginhub rune-kit/rune --plugin @rune/analyticsThis skill uses the workspace's default tool permissions.
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.
Syncs Plans.md task markers with git status, commits, diffs, and agent traces. Detects drift between planned and actual progress, proposes updates (TODO/WIP/done), generates summary and retrospective. Use for 'sync-status' or progress checks.
Audits post-implementation plans against changes by parsing checkboxes for completeness and accuracy. Supports autonomy modes (Autopilot, Critical, Verbose) and file-review. Invoke via /verify-plan.
Reviews PRs strictly against their originating plan, flagging in-scope undone work as always blocking to prevent scope leaks and pipeline waste.
Share bugs, ideas, or general feedback.
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.
cook (L1): Phase 6.6 scope drift detection when files touched > plannedteam (L1): after each parallel workstream completes, before mergerescue (L1): during safeguard phase to detect unplanned changesplan (L2): optional scope validation after plan acceptanceNone — pure L3 monitoring utility.
Read the original task/plan from one of these sources (check in order):
.rune/progress.md — use Read on D:\Project\.rune\progress.md (or equivalent path)Extract from the plan:
Run Bash with git diff to see what has actually changed:
git diff --stat HEAD
Also check staged changes:
git diff --stat --cached
Parse the output to extract the list of changed files.
For each changed file, determine if it is:
Rules for "natural dependency" (counts as IN_SCOPE):
Rules for OUT_OF_SCOPE (counts as creep):
Compute Drift Percentage — the ratio of out-of-scope changes to total changes:
drift_pct = (out_of_scope_files / total_files_changed) × 100
Classify drift into a 4-tier system:
| Drift % | Level | Status | Action |
|---|---|---|---|
| < 10% | ON TRACK | ON_TRACK | No action needed. Proceed normally. |
| 10-25% | MINOR DRIFT | MINOR_DRIFT | Flag out-of-scope files. Suggest trim or acknowledge as intentional. Continue. |
| 25-50% | SIGNIFICANT DRIFT | SIGNIFICANT_DRIFT | Pause recommended. Present drift report to user. Re-scope before continuing. |
| > 50% | OUT OF CONTROL | OUT_OF_CONTROL | Block. More unplanned work than planned. Escalate to orchestrator. Require re-alignment before ANY further work. |
Edge case: If total planned files = 0 (no plan loaded), use file count thresholds instead:
Output the following structure:
## Scope Report
- **Planned files**: [count from plan]
- **Actual files changed**: [count from git diff]
- **Out-of-scope files**: [count]
- **Drift**: [X]% ([level])
- **Status**: ON_TRACK | MINOR_DRIFT | SIGNIFICANT_DRIFT | OUT_OF_CONTROL
### In-Scope Changes
- [file] — [matches planned task]
### Out-of-Scope Changes
- [file] — [reason: unplanned feature | unrelated refactor | unplanned dep]
### Recommendations
- [ON_TRACK]: No action needed. Proceed.
- [MINOR_DRIFT]: Review [file] — consider reverting or acknowledging as intentional.
- [SIGNIFICANT_DRIFT]: PAUSE. Drift is [X]%. Re-align scope with original plan. Suggested cuts: [files to revert]
- [OUT_OF_CONTROL]: STOP. [X]% of changes are unplanned — more drift than planned work. Present full report to user/orchestrator. Do NOT continue until re-scoped.
## Scope Report
- Planned files: 3 | Actual: 5 | Out-of-scope: 2
- Drift: 40% (SIGNIFICANT_DRIFT)
### Out-of-Scope Changes
- src/components/NewWidget.tsx — unplanned feature
- docs/new-feature.md — documentation for unplanned feature
### Recommendations
- PAUSE. Drift is 40%. Re-align scope with original plan.
- Suggested cuts: revert src/components/NewWidget.tsx + docs/new-feature.md (reduces drift to 0%)
Known failure modes for this skill. Check these before declaring done.
| Failure Mode | Severity | Mitigation |
|---|---|---|
| Classifying test files for planned code as out-of-scope | MEDIUM | Test files for planned source files are always IN_SCOPE — natural dependency |
| Classifying lock file changes as out-of-scope | LOW | package-lock.json, yarn.lock, Cargo.lock are always IN_SCOPE |
| Over-escalating drift (e.g., 1 extra file = OUT_OF_CONTROL) | LOW | Use drift percentage, not gut feeling. 1 extra file out of 10 = 10% = MINOR_DRIFT, not panic |
| Plan not loadable (no TodoWrite, no progress.md) | MEDIUM | Ask calling skill for plan as text description before proceeding |
| Scope check against plan but not against stated intent | MEDIUM | Plan-based scope guard catches file drift; review Step 6.6 (Scope Drift Detection) catches intent drift. Both should run for full coverage |
| Artifact | Format | Location |
|---|---|---|
| Scope Report | Markdown (drift %, 4-tier level, recommendations) | inline |
| In-scope file list | Classified list | inline |
| Out-of-scope drift report | File list with reasons | inline |
| Recommendations | Actionable list | inline |
~200-500 tokens input, ~100-300 tokens output. Haiku. Lightweight monitor.
Scope guardrail: scope-guard reports drift and advises — it does not revert files, block commits, or modify code. Override decisions belong to the calling orchestrator or the user.