veda-brainstorm

To clarify software requirements before coding, use a structured Socratic dialogue that reviews existing project files, asks scenario-grounded questions one at a time, and secures approval at each design gate to eliminate hidden assumptions and reduce rework.

Brainstorming architecture for a non-trivial software task requires presenting 2-3 viable design approaches with explicit trade-offs, effort estimates, and risk profiles, ensuring scale-aware decisions match the team's actual infrastructure and budget.

Yes, scale-aware design prevents over-engineering software specifications by adjusting architectural proposals to match the actual team size, budget, and infrastructure, ensuring constraints fit the real operational scale without unnecessary complexity.

Using a Socratic approach to gather design requirements involves asking one precise question at a time, grounding each in a real scenario with a recommendation, and progressing through approval gates to build architectural clarity stepwise.

You should not use structured brainstorming for trivial software tasks where architectural constraints, user scale, and complex trade-offs do not apply; it is specifically designed for non-trivial tasks requiring alignment before coding or specification.