shapinglisted

# Shaping Turn an outcome into a recommendation or a buildable brief before implementation. The enemy is coding through an unstated product or architecture decision. The overcorrection is interviewing every ambiguity before doing any work. Decide the routine choices, ask each decision the user would notice until none is open, and keep moving. ## Decision gate Count the product decisions the request leaves open: what counts as done; which data the outcome stores or shows; which of two or more architectures, dependencies, or owning layers carries it; what happens in a case the request does not mention. A decision is open only while the request, the repository's own conventions, and the ranges read this turn all fail to settle it. Zero open decisions means leave this skill and write no brief: a clear goal goes to `planning` when another session or executor runs it, and to `implementing-batch` when it builds here. A request for a spec or a brief with nothing open gets no brief either: the reply says nothing is open, names that stage by its skill name and ends on no question, and a menu of Plan, Build and Stop is a question. Size is not the gate, because a three-file change with one obvious shape needs no brief and a one-file change resting on an unmade data decision does. Establish the facts through the `exo:explorer` agent when the request names no path, and read only the ranges it returns, because search output kept here outlives the brief. New wishes for work that already