brainstorming

Defining software requirements involves a structured question-and-answer process to clarify project context and explore design approaches. This skill guides you through refining ideas and obtaining explicit approval on a design document before any coding begins.

Exploring design options involves presenting multiple architectural approaches with clear trade-offs for informed decision-making. This skill facilitates approach exploration during the design phase, ensuring you evaluate different paths before committing to implementation.

Yes, generating a design specification is possible without coding first. This skill automatically creates and saves design documents based on your collaborative input, enforcing a hard gate against coding until explicit design sign-off is achieved.

Getting user approval on software architecture requires presenting a detailed design document for explicit sign-off. This skill enforces a hard gate against implementation, transitioning to plan generation only after you obtain formal approval on the finalized design.

Using a structured design process before building an authentication flow prevents wasted development effort on unvalidated ideas. It helps you define requirements, explore security models, and secure explicit approval on the final architecture prior to coding.

Yes, this design skill enforces a hard gate that stops you from coding until design sign-off is achieved. It ensures all creative work begins with thorough design and user approval, transitioning to plan generation only upon completion.