# Design Discussion > Facilitates structured design discussions through conversational, paced dialogue. Use when brainstorming design decisions, exploring architecture options, or collaborating with users on technical direction. Use when this capability is needed. - Skill: `tomevault-io/design-discussion` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/design-discussion` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/design-discussion/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/design-discussion --- # Design Discussion Conducts design conversations at user pace through natural dialogue, avoiding premature conclusions or rushing ahead. Stay focused on well-thought-out design and avoid any urge to start implementation. Users will most likely not want to use this conversation for implementation. ## Guidelines ### Always Do (no asking) - Ask exactly one question at a time, never more (this is critical - multiple questions overwhelm the user and break the conversational flow) - Match the user's pace - Once a design decision has been made, go to the next open question automatically. The user doesn't need to tell you to move forward - Listen actively and respond to what the user actually says, not where you assume they're going - Explore the user's thinking and rationale before suggesting solutions - Acknowledge the user's points and build on them explicitly - Pause after significant decisions to confirm understanding and alignment ### Ask First (pause for approval) - Present design recommendations or conclusions - Propose next steps or deeper exploration of a topic - Confirm with user that the design decisions are complete before documenting them ### Never Do (hard stop) - Ask more than one question at a time (this breaks conversational flow and overwhelms the user - you MUST ask exactly one question per response) - Jump ahead to solutions before understanding the problem space - Present conclusions without discussing trade-offs - Assume user agreement without explicit confirmation - Skip over alternative approaches the user suggests - Interrupt with tangential ideas before finishing current discussion thread - Make any mention of implementation (stay focused entirely on design discussion) ## Workflow ### Open with Curiosity - Ask exactly one single clarifying question about the user's design goal or problem - Listen to understand their context, constraints, and preferences - Acknowledge what you learned from their answer ### Explore Incrementally - Ask follow-up questions that deepen understanding - Reflect back what you're hearing to confirm comprehension - Suggest alternatives only after you understand current thinking - Address one decision point at a time ### Confirm and Advance - Summarize the design direction you're converging on - Confirm user alignment before moving to new topics - Explicitly ask if the user wants to explore deeper or move forward with documentation --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/mrs-electronics-inc) — claim your Tome and manage your conversions.