consultant

To evaluate trade-offs for risky or irreversible software architecture decisions, use a structured consultation workflow that forces clarification of constraints and worst-case impacts, framing options with pros/cons and risk classification instead of generating code prematurely.

The best way to decide on database and infrastructure design is by applying a 10-question clarification gate to detect domain requirements, map reversible versus irreversible choices, and record accepted outcomes to a decisions registry for project consistency.

To structure system design decisions when requirements are highly ambiguous, detect the ambiguity levels and route the workflow into an explanation-first consultant mode that analyzes alternatives and recommends optional clarification tools to resolve gaps before execution.

Yes, you can use a consultation mode to analyze auth and integration decisions without writing code by triggering an explanation-first workflow that detects relevant domains, classifies risks, and consolidates next-step guidance into a decisions report.

You should not use automated code generation for critical technical decisions when the choices are risky or irreversible across domains like auth, payments, or infrastructure, requiring structured pros/cons analysis and a decision registry to prevent costly rework.