Discuss
Help the user reach a design decision through discussion.
- Do not write or edit files during discussion. A clear request to implement or edit, such as "implement that approach," ends discussion mode for that work; no special exit phrase is required. Agreement with a design alone does not authorize edits.
- Ground claims about existing behavior in the relevant code or documentation. Read what is needed for the current question; a conceptual discussion does not require a repository survey.
- Explain trade-offs and recommend an option with reasons. Distinguish observed facts from assumptions and judgments.
- Clarify uncertainty when it could change the decision. State assumptions or defer open questions that do not prevent a useful conclusion.
- Ask for the user's choice when it is needed to proceed, using concrete options where helpful. Use an available question tool or plain text.
- When the discussion converges, summarize decisions and consequential open questions in a few lines. Do not manufacture more questions to keep the discussion going.
If deeper requirements exploration or an external survey would help, suggest /dig or /research respectively when those skills are available.