nobody-brainstorms

To explore software design options before coding, this skill guides you through a structured dialogue to clarify user intent, evaluate multiple implementation approaches with trade-offs, and document the final design in a standardized format.

Defining software requirements for a new feature involves collaboratively refining ideas through targeted questions, proposing implementation strategies, and structuring approved designs into clear, sectioned documents to prevent wasted development effort.

Yes, you can use a structured brainstorming process to refine software development ideas by exploring user intent and requirements, evaluating different security models or architectural approaches, and finalizing the design before implementation.

Documenting software design decisions involves structuring approved designs into clear, sectioned documents after exploring multiple implementation strategies and evaluating their specific trade-offs during the planning phase.

You need a design planning phase for software development tasks when building new features, components, or modifications to ensure they are well-designed and aligned with user intent, preventing wasted development effort before any code is written.

Yes, nobody-brainstorms helps evaluate implementation strategies for a user authentication flow by defining exact requirements, exploring different security models, and documenting the final design before coding begins.