[FEATURE] scope-lock prefix to suppress speculative additions

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude frequently adds speculative, out-of-scope items to plans and proposals — extra steps, future-proofing suggestions, or tangentially related improvements that were never requested. This is helpful
in some contexts but counterproductive when a user wants a strictly literal, minimal response.

There is currently no signal to suppress this behavior without relying on prompt wording or memory/instructions that may not be respected consistently.

Proposed Solution

Introduce a special prefix character (e.g. !) that, when placed at the start of a message, instructs Claude to be maximally literal and strictly in-scope:

• No speculative additions
• No out-of-scope suggestions
• No "while we're here" improvements
• Answer or implement exactly what was asked — nothing more

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

! add groupByCurrentUser prop to LocationsList

Claude should add the prop and nothing else — no reformatting nearby code, no suggesting related refactors, no mentioning potential improvements.

Additional Context

Why a prefix rather than a prompt phrase

Prompt phrases like "don't add anything out of scope" are interpreted loosely and inconsistently. A dedicated prefix would be a hard, unambiguous signal at the instruction layer, similar to how ! in a
shell means "run this directly."