brainstorming

To validate software design assumptions before implementation, enforce a collaborative design validation phase covering context exploration, clarifying questions, approach trade-off analysis, and mandatory design approval gates. This structured workflow prevents wasted implementation work caused by unexamined requirements and skipped design phases.

Pre-development spec writing is the process of documenting a formal design specification before any coding or scaffolding begins. You need it for all software project scopes, from simple utilities to complex multi-subsystem platforms, to eliminate wasted implementation work caused by skipped design phases and unexamined assumptions.

Planning a new feature design from an initial idea involves guided collaborative dialogue where you refine user intent, requirements, constraints, and success criteria one question at a time. You then compare 2-3 approach trade-offs, present a full design for approval, and write a formal spec before implementation planning handoff.

Structured design validation applies to all project scopes from simple utilities to complex multi-subsystem platforms. It covers feature creation, component building, functionality additions, and behavior modifications, ensuring even seemingly simple projects avoid wasted implementation work from unexamined assumptions.

The best way to compare software design approaches is through a mandatory design approval gate that presents 2-3 approach trade-offs for user review. This structured comparison ensures you analyze different architectural options, like session versus JWT for authentication, before any implementation work starts.

To refine vague project requirements, use a guided collaborative dialogue that asks one clarifying question at a time. This structured approach systematically refines user intent, technical constraints, and success criteria until requirements are concrete enough to support formal spec writing and implementation planning.