scope

Scope

This skill holds an edit to the request. It reads the smallest literal meaning, keeps everything that already worked and accounts for every item the user sent.

The smallest reading wins

A change outside the named element is a finding unless the user asked for a sweep. One short question before a broad change is not a finding. Press hardest on short messages that point at one element, on batched messages and on refactors.

Deleting what nobody asked for belongs to restraint. Proving the change works belongs to verify.

Every ask gets an answer

Split the message into numbered items and add the open items from earlier turns. Close with the same list, each item done or not done with the reason. Doing the first of four asks is scope-list-every-ask.

The named element and nothing around it

Restate the target in a few words. "The card" means the card, not the page around it. Restyling the whole shell for a top bar request is scope-smallest-reading. When two readings fit, ask one short question.

Earlier instructions still stand

Before editing, read the user's earlier corrections in the thread and the rules in the repository. Re-adding something they removed is scope-remember-instructions. A value they gave, such as 16px of left padding, stays. Guessing a new one is scope-keep-given-values.

What worked keeps working

Before a refactor, list the features, buttons and states that exist now, then check each one after. A dropped back button is scope-keep-what-worked. When fixing one property, keep the others. Fixing a clip by removing the width animation is scope-no-collateral.

Unshipped work is done now

Work that has not shipped is not split into phases or marked out of scope without asking. A "phase 2" list is scope-no-phasing. While planning, plan only. Editing files before the plan is approved is scope-plan-means-plan.

An explanation is the answer

When the user asks how something works, explain it and wait. Answering "how does this work" with a diff is scope-explain-when-asked.

The pair

Every check is a pair. The broken line sits beside the line that replaces it.

Rule	Broken	Replacement
scope-list-every-ask	The first of four asks done, three dropped	Four numbered items, each reported
scope-smallest-reading	"Fix the top bar" restyles the whole shell	Only the top bar changes
scope-remember-instructions	Dots the user removed come back	Earlier turns read before editing
scope-keep-given-values	Left padding re-guessed as 12px	The 16px the user gave
scope-keep-what-worked	A refactor drops back and forward buttons	Before and after feature list, both buttons kept
scope-no-collateral	The clip is fixed and the width animation is gone	Clip fixed, width animation kept
scope-no-phasing	"Saved filters: phase 2"	Built now, or one question
scope-plan-means-plan	Files edited during planning	Plan only until it is approved
scope-explain-when-asked	"Explain how it works" answered with a diff	An explanation, then wait

Reporting

Severity. HIGH is a dropped feature, or an earlier instruction undone. MEDIUM is a change outside the named element, or an ask left unreported. LOW is a question asked where one reading was plain.

Format. One finding per root cause, citing the request when no file applies:

file:line - [rule-id] what is wrong
request 2 - [rule-id] what is wrong

Then a Rule | Count | Severity summary. Block when any HIGH remains, Approve otherwise. Never Approve a diff you did not read. Mark every check you could not run as Not verified.