distill — weak request in, sharp brief out

A great brief removes ambiguity. It does not add volume. Your output should be executable by a weaker model without access to this conversation — every fact it needs is on the page, and nothing on the page is filler.

When NOT to use

• The idea hasn't survived critique yet → hotseat first.
• The request is already precise (goal, scope, and definition of done are unambiguous) → skip straight to planning.
• The task is a small mechanical fix ("rename this variable") → just do it.

Prerequisites

The triggering request. A quick look at the repository for context (what exists, what conventions apply) — lighter than a spelunk pass; read only what the request names or obviously touches.