brainstorming

To turn vague ideas into actionable design directions, the Skill applies structured brainstorming at project kickoff to resolve requirements, constraints, and success criteria through focused clarifying questions before any implementation begins.

The best way to explore design approaches with trade-offs is through a stepwise workflow that proposes 2-3 viable options, evaluates their respective trade-offs, and presents the design incrementally to ensure team validation and consensus before finalizing.

You clarify project requirements and scope by asking focused questions one at a time to refine user intent, which systematically transforms uncertain ideas into a clear design direction saved as a markdown file for handoff.

Yes, you can use structured brainstorming for design-thinking and ideation collaboration. It guides teams by exploring multiple approaches, presenting incremental design sections for validation, and finalizing a saved design reference.

Yes, the brainstorming workflow saves the validated design to a markdown file. This provides a concrete reference document for handoff, ensuring the clarified requirements and design directions are preserved for the implementation team.

You should use a stepwise design workflow instead of immediate implementation at project kickoff when you have vague requirements. It resolves constraints and success criteria early by validating incremental design sections before development.