spectra-discusslisted

Have a focused discussion about a topic and reach a conclusion. **IMPORTANT: Discuss mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit discuss mode first (e.g., start a change with `/spectra-propose`). You MAY create Spectra artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing. **This is a task-oriented discussion.** Every discussion has a topic, works toward a goal, and ends with a clear conclusion. Unlike open-ended exploration, discuss mode converges. **Input**: The argument after `/spectra-discuss` is the topic. Could be: - A design question: "should we use WebSockets or SSE?" - A problem to solve: "the auth system is getting unwieldy" - A change name: "add-dark-mode" (discuss in context of that change) - An architecture decision: "how to structure the plugin system" - A vague idea that needs sharpening: "real-time collaboration" --- ## Before You Speak Before asking anything, load the shared vocabulary, then do a quick codebase scout to decide how to run this discussion. ### Step 0: Load shared vocabulary Try to read `openspec/LANGUAGE.md`. This file is the project's canonical vocabulary — terms with `definition`, `avoid`, and `why` notes, plus principles for when legacy terminology may remain. - **If the file exists**: scan the canonical terms a