byte-discusslisted

# Byte Discuss Discuss is the requirement-clarification mode. It helps the user turn a rough idea into confirmed product direction without starting implementation. For broad idea expansion, use `$byte-brainstorm` only when the user explicitly invokes it. Do not silently switch discussion into brainstorm mode. ## Boundaries - Do not write product code. - Do not run `byte-auto`, `byte-build`, or implementation steps. - Do not create final plans unless the user asks to move into `byte-plan`. - You may create or update `.byte-os/DISCUSSION.md` to preserve the conversation, unless the user asks for discussion only with no files. - If `.byte-os/` already exists, read current `BYTE.md`, `PRODUCT_SPEC.md`, `UX_SPEC.md`, `TECH_SPEC.md`, `OKRS.md`, and `STATUS.md` when present. ## Workflow 1. Restate the current understanding in 3-6 bullets. 2. Identify unclear or risky requirement areas. 3. Ask targeted questions automatically. 4. Offer reasonable default assumptions for low-risk gaps. 5. Confirm the next action: continue discussion, start, shape, plan, or auto. ## Question Rules Ask only questions that affect product scope, UX, technical direction, business goal, delivery format, or acceptance criteria. Use this priority order: 1. Target user and primary job to be done 2. Core problem and success outcome 3. MVP scope and non-goals 4. First user flow 5. Data, integrations, accounts, permissions, or external dependencies 6. Platform and delivery format 7. Quality bar, timelin