oc-brainstorminglisted

# Brainstorming Ideas Into Designs Turn an idea (issue, request) into a fully-formed design and spec through natural collaborative dialogue **with the operator**. `build` keeps a design discussion in the same session and starts its normal entry policy only when the operator asks for delivery. Never infer that a design discussion alone authorizes implementation. This skill runs inside the `build` (primary) agent. Its output is the approved (or multi-agent-validated) spec that Phase 1 hands to the `planner`. ## Interactive vs headless - **INTERACTIVE:** ask the operator **one question at a time**; present design; wait for approval. - **Autonomy directive — AUTONOMOUS (local):** when the operator explicitly says "sem parar", "sem me perguntar", or equivalent, use the HEADLESS evidence-and-adversary workflow without waiting. This is prompt-level delegation only: OpenCode does not inject a continuation or re-open an idle session. Ask only when two viable choices change the observable product behavior or contract; select and record the least-invasive engineering option when the contract is the same. - **HEADLESS** (autonomous / VPS cron / `$HARNESS_OBSERVABILITY_RUN_PATH` / `$HARNESS_OC_DATA_HOME` / trigger says "without asking"): **do not wait for a human**. Simulate exploration with **read-only** investigation + optional fan-out `task` exploration lenses (user-journeys, edge-cases, constraints), synthesize a spec from the trigger + codebase, then run one primary **sp