# Scope Lock

> Keep implementation or review work inside the user's authorized outcome and protect unrelated work. Use when requirements are sprawling, the repository is dirty, a change risks expanding into refactoring, or the user asks to prevent scope creep. Do not use for open-ended exploration where discovering a wider scope is the goal.

- Skill: `denizaslan36/scope-lock` (Agent Skill)
- Install (CLI): `npx skillmds@latest add denizaslan36/scope-lock`
- Raw SKILL.md: https://api.skillmd.com/api/skills/denizaslan36/scope-lock/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: denizaslan36 (https://skillmd.com/u/denizaslan36)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/denizaslan36/scope-lock

---


# Scope Lock

Define the smallest complete change and guard its boundary.

## Lock the Scope

1. Derive a compact contract from the request:
   - **outcome** — what must become true;
   - **allowed surface** — files, systems, or behaviors that may change;
   - **constraints** — compatibility, style, safety, time, and explicit preferences;
   - **non-goals** — adjacent improvements not required for completion.
2. Inspect the relevant existing state before editing. Treat unrelated modifications and untracked files as user-owned.
3. Evaluate every proposed change with two questions:
   - Is it necessary for the outcome?
   - Is it authorized by the request?
4. Exclude opportunistic refactors, formatting churn, dependency upgrades, and cleanup unless they are required or separately approved.
5. If a newly discovered dependency materially expands risk or effort, pause and explain the boundary change. Ask only when different answers would lead to meaningfully different work.
6. Before handoff, compare the actual diff or output with the contract and remove accidental scope expansion without overwriting unrelated user work.

## Boundary Decisions

- **Inside** — necessary and authorized: proceed.
- **Incidental** — harmless but unnecessary: omit.
- **Blocked** — necessary but needs new authority or information: report and pause.
- **Separate** — valuable follow-up outside this task: mention briefly only if it materially helps.

Do not create a scope document unless the task is complex enough to benefit from one. The contract may remain an internal working summary.