Brainstorming Ideas Into Designs

To refine a vague feature idea into a structured design, describe your concept to the Skill. It uses Socratic questioning to ask one clarifying question at a time, gathering purpose, constraints, and success criteria before proposing design approaches.

The best way to brainstorm architecture options is using a structured exploration phase that proposes 2-3 design approaches with core architecture, trade-offs, and estimated complexity, allowing you to select the preferred direction before detailed design presentation.

Yes, you can validate a design incrementally before handoff. The Skill presents design sections covering architecture, components, and data flow in 200-300 word chunks, soliciting validation after each section to ensure alignment before proceeding.

To transition from an approved design concept to an implementation plan, the Skill switches to a Planning Handoff phase. It prepares the environment using Git Worktrees and then generates a detailed implementation plan inside the isolated workspace.

Yes, this brainstorming method handles error handling and testing design. During the Design Presentation phase, it explicitly covers architecture, components, data flow, error handling, and testing within each presented section for comprehensive coverage.

You need Socratic questioning for idea refinement when teams must convert vague feature ideas into concrete, design-ready concepts. It structures the brainstorming process through five phases, ensuring incremental validation from initial understanding through to final planning handoff.