recipe-refine-visualslisted

**Context**: Refine the concrete tokens used by a named prototype or downstream design consumer. The output remains `docs/product/design/brand-direction.md` so consumers read one approved source. ## When to Use - `brand-direction.md` contains concrete tokens, or the user names a consumer that now requires them - A design expert wants to refine the values that affect that consumer ## Orchestrator Definition **Execution Protocol**: 1. **Follow the refinement flow** defined below 2. **Stop at every `[STOP — BLOCKING]` marker** — present findings and CANNOT proceed until user explicitly confirms ## Workflow Overview ``` Input (brand-direction.md + named token consumer) ↓ 1. Context Reading → Read brand direction + design principles + personas ↓ 2. Token Review → Present only Concrete Tokens that affect the named consumer ↓ 3. Expert Refinement → Expert retains or refines consumer-relevant values [Stop: User confirms result] ↓ Output: Updated Concrete Tokens in docs/product/design/brand-direction.md ``` ## Execution Decision Flow ### 1. Context Reading **Gate: Approved brand direction and a named consumer requiring concrete values must be inspectable. Existing tokens may be refined; absent tokens may be added only for that consumer. Return the exact missing decision when either input is unavailable.** Read: - `docs/product/design/brand-direction.md` — Design Intent, Decision-Relevant Direction, and current Concrete Tokens when present - `docs/product/desi