brainstorming

To turn a vague software feature request into an implementation-ready plan, use a Socratic questioning loop to extract intent, discover constraints, and resolve ambiguities before synthesizing a final design brief with acceptance criteria.

Evaluating architectural trade-offs before coding involves generating multiple viable approaches and comparing them on complexity, maintainability, performance, and time-to-ship to recommend a primary approach with clear rationale.

Mapping edge cases for unfamiliar system integrations requires targeted clarification questions that surface hidden constraints like timelines, scalability requirements, and specific user workflows before finalizing the design.

You need design brief planning when a task involves multiple architectural trade-offs, unclear scope, or integration with unfamiliar systems, preventing wasted engineering effort by refusing to generate code until the spec is confirmed.

A pre-coding design brief contract should include the problem statement, chosen approach with rationale, explicit non-goals, acceptance criteria, and a detailed task breakdown to guide implementation.

Brainstorming software requirements works without initial technical specifications by applying a Socratic questioning loop to extract core intent and resolve ambiguities directly from a vague feature request.