Validate proposed code changes against user requests before editing.
npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill stay-in-lane
Please help me install this Agent Skill. Skill: stay-in-lane Source: https://github.com/ElliotJLT/Claude-Skill-Potions/tree/main/skills/stay-in-lane Command: npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill stay-in-lane
The Stay In Lane skill prevents scope creep by verifying that proposed changes match the user's original request before editing code, reducing misfires and unnecessary refinements.
Use Stay In Lane before any code modification to confirm the scope of the requested change. Provide the user’s request and the proposed change, then evaluate:
High-intent search queries and answers about installing and using this skill.
Scope creep prevention starts by validating proposed changes against your original request before editing. Use a decision matrix to classify each change as Proceed, Stop, or Adjacent, ensuring modifications stay aligned with intent and reducing unnecessary refinements.
When adjacent improvements emerge during reviews, complete the requested change first, then document adjacent work separately for later. This keeps focus on the primary task while capturing secondary improvements without derailing the current scope.
Before any modification, apply a scope-match checklist: compare the proposed change directly against the user's request using the decision matrix. If Match is Yes, proceed; if No, halt and request clarification; if Adjacent, complete the request first.
Yes. Stay In Lane applies across development sessions, code reviews, and pair programming. Use the before-change checklist and adjacent-work guidelines in each context to maintain focus and prevent scope creep consistently.
Stop the modification and prompt for clarification. Mismatched changes indicate scope creep risk. Use the decision matrix to determine whether the change is truly out of scope or qualifies as adjacent work that should be deferred.
Refactors can drift into unrelated improvements, multiplying risk and review cycles. Scope verification ensures refactoring stays focused on the stated goal—structural change, performance, or clarity—without bundling unrelated enhancements.
devmuslimGenerate a formal change request document for project scope, timeline, or budget changes.
johannesfritzScore backlog items using RICE, ICE, and MoSCoW frameworks.
jmaglyAutomate multi-stakeholder approval routing for marketing assets with SLA tracking.
0xtaoistScore test usefulness by Impact × Probability and write a markdown audit.
