define-scopelisted

# Shaping Turn a request into a confirmed brief, so nobody codes through an unmade decision. The enemy is building on a guess. The overcorrection is asking what the code already answers. ## Gate - Zero open decisions means leave this skill and write no brief; hand the goal to `build-change`. The exception is two or more order dependencies: write the brief unasked, from `## Listing tasks` on. `A → B` is one when B cannot build, test or keep its data before A lands. An open decision is one the user would notice that neither request nor code settles. - Asked for options, give directions, recommended first, and write no file. - New wishes for briefed work reopen that brief, since two briefs for one outcome drift apart. ## Interview 1. **Ask or decide.** Ask only what is costly or irreversible; decide the routine, a visible but cheap point included. Costly means stored data format, a public interface, a paid service, a deletion, or access rights and security. 2. **Look facts up** in the code while the user answers. 3. **Root first.** Ask what other decisions hang on, and finish its branch first. 4. **Sort each open point into a bin.** Costly (step 1) asks; answerable by running something (which approach works, how it feels, whether it is fast enough) goes to `try-idea` and comes back as a decision, never a question; routine you decide and list as an assumption. 5. **Bundle every bin-1 question and bin-3 assumption into one message**, in the shape below. No bin-1 p