jds-think

Requirement clarification and design before coding prevent wasted cycles by guiding users through structured questions, approach options, and a formal specification. This stage-based workflow enforces user confirmation before any planning or implementation begins.

A formal specification template structures software design by documenting approach options, design sections, and inline reviews. It acts as a gate to ensure thorough exploration and requirement clarification occur before handing off to the planning phase.

To create a design specification for unclear requirements, use an ask_user-based questioning protocol to explore the problem. Propose multiple approaches, draft design sections, and secure user confirmation before proceeding to implementation planning.

Yes, a stage-based workflow enforces user confirmation by requiring explicit approval at each phase. It moves sequentially through requirement exploration, design specification, and inline review before formally handing off to the planning stage.

The best way to design before planning is to apply a structured gate that clarifies requirements through targeted questions, proposes viable approaches, and drafts a formal spec. This prevents miscommunication and aligns stakeholders before coding starts.

Use a design and exploration gate for software engineering tasks with unclear requirements or potential domain skill overlaps. It prevents wasted effort by mandating rigorous exploration, approach selection, and formal specification before planning.