Menu
Assess whether a proposed change fits the current work context or represents scope creep
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit context window consumption across LOTRAOM agents, skills, rules, MCP servers, and CLAUDE.md. Report token estimates, flag bloat, recommend trims.
Hard-block Edit/Write outside a chosen directory. Use to scope-lock edits during a focused fix or refactor. Pair with /unfreeze to release.
Six-phase root-cause debugging for crashes, build failures, or "why is this broken" reports. Iron Law - no fixes without root cause. Auto-engages /freeze.
Release the directory edit lock set by /freeze. Edit and Write are unrestricted again. No-op if /freeze was never set.
Dispatch an independent Codex verification job for the current changes
Inspect all changed files, group by logical concern, and guide atomic per-concern commits
| name | scope-check |
| description | Assess whether a proposed change fits the current work context or represents scope creep |
| argument-hint | ["description of proposed change"] |
Evaluate whether the following proposed change aligns with the current work context.
$ARGUMENTSRead recent CHANGELOG entries — Check CHANGELOG.md for the [Unreleased] section and last 2-3 dated sections.
Review recent commit history — git log --oneline -15
Check in-progress work — git diff --name-only and git diff --staged --name-only
Identify current work theme — Which feature area, which project component (mod/launcher/server/devops)?
Assess the proposed change:
Natural Extension (GREEN): Directly relates to current files, fixes a discovered bug, completes incomplete work, small improvement in same area.
Adjacent Work (YELLOW): Related but different feature area, could be deferred, requires context-switching.
Scope Creep (RED): Unrelated feature area, requires new infrastructure, would interrupt incomplete work.
Recommendation — GREEN/YELLOW/RED with reasoning. If YELLOW/RED: defer, create GitHub issue, or suggest minimal version.
READ-ONLY assessment. Do not make code changes.