vibe-change-speclisted

# Vibe Change Spec Skill Handles scope changes at any point during the build — safely, in the right order. Always assesses impact first. Always waits for confirmation. Never edits files speculatively. **Always run in Plan Mode (Shift+Tab). Do not write any code in this skill.** --- ## The O'Reilly principle this enforces **Drift prevention** — scope changes must be logged explicitly. An informal "just quickly add X" mid-task produces a codebase that doesn't match its documentation. When review: runs, it finds violations with no logged context. change: prevents this by stopping work, assessing impact, and updating all affected documents before building continues. --- ## When this skill runs Any time the user signals a scope change: - `change: add dark mode before we build screens` - `change: remove social login — email only` - `change: add push notifications to backlog` - `change: promote push notifications to active` - `change: rename "ideas" to "posts" throughout` - `change: revert the PDF attachment change we made last week` - Natural language: "actually I also want X", "I forgot Y", "can we cut Z" --- ## Step 1 — Understand the change Extract: - What is being added, removed, modified, renamed, or reverted - Whether it's a new feature, requirement tweak, removal, rename, backlog op, or revert - Whether it's urgent (insert now) or deferred (backlog) If ambiguous, ask the clarifying questions you actually need — batched together, not one at a time. Confirm: > "Go