discuss

To align on architecture decisions before implementation, use a structured, read-only discussion process that gathers context and asks one clarifying question at a time. This approach helps evaluate tradeoffs and goals collaboratively without generating any code prematurely.

Yes, you can clarify product requirements during a design review by enforcing a read-only exploration phase. The process inspects existing repositories and documentation to guide alignment through opinionated recommendations, strictly prohibiting file generation or implementation artifacts.

The best way to break decision paralysis during technical planning is to adopt an opinionated collaboration approach where the agent recommends a default path instead of remaining neutral, followed by asking high-impact questions one at a time to move toward alignment.

No, collaborative design discussion requires read-only access to project files and web resources. It strictly prohibits modifying files or generating implementation artifacts, ensuring the focus remains entirely on gathering context and aligning on decisions.

You should avoid using an opinionated agent for architecture discussions if your goal is to generate code, produce implementation artifacts, or if you need a neutral, unbiased exploration of options without receiving a recommended default approach.

To start a focused conversation to debate tradeoffs, initiate a read-only discussion by stating your topic, such as planning an authentication strategy. The agent will gather context, state a recommended approach, and ask one clarifying question at a time.