csp-scope-guardlisted

# Scope Guard Detect scope creep early and enforce disciplined boundaries around the current task. ## When to Use - A feature request grows from "add a button" to "rebuild the dashboard" - You notice yourself editing files unrelated to the stated task - A bug fix reveals a "nearby improvement" that wasn't part of the original scope - The word "also" or "while we're at it" appears in a request - A task estimate has doubled without a clear reason ## When NOT to Use - The original requirement was genuinely misunderstood and needs correction - A critical security vulnerability is discovered during implementation - The user explicitly reprioritizes and accepts the tradeoff ## Scope Creep Detection Signals | Signal | Severity | Action | |--------|----------|--------| | "While I'm here" edits | Medium | Stop. Is this in the current task? | | New dependency added mid-task | High | Does this dependency serve the original goal? | | Refactoring triggered by a feature | High | Separate into a follow-up task | | "Wouldn't it be cool if..." | Critical | Park it. Write it down. Don't build it now. | | Touching >5 files for a "simple" change | Critical | Re-evaluate scope. Something expanded. | | New UI element not in original spec | High | Confirm with stakeholder before proceeding | ## Process 1. **Define the boundary** — Before starting, write a one-sentence scope statement: "This task does X and nothing else." 2. **Check each change against the boundary** — For every file edit,