Auto-Scope

Before diving into a substantive coding task, name the files that matter and the ones that don't — so the work doesn't open by reading the whole repo to orient.

The output is an in-context scope brief, not a file on disk and not a lock on the filesystem. Any file can still be read later; the brief steers the default, it doesn't enforce it. The win is that 5–15 named files replace an exploratory sprawl.

1. Self-gate — decide whether to fire at all

Run only when the task plausibly touches multiple files or an area not seen this session.

Skip silently — emit nothing, not even a note that you skipped — when the task is any of:

• a single-file or one-line edit
• a question, explanation, or review with no code change
• continued work in an area already scoped earlier this session

If you're skipping, say nothing about scoping and proceed normally. A "I decided not to scope this" line is itself noise.

2. Discover — use whatever search the environment has