brainstorming

Guide structured brainstorming to turn raw ideas into design concepts.

Updated Dec 13, 2025
One-click install
npx skills add https://github.com/OTSOU-CODE/OTSOU --skill brainstorming-otsou-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/OTSOU-CODE/OTSOU/tree/main/.agent/skills/brainstorming
Command: npx skills add https://github.com/OTSOU-CODE/OTSOU --skill brainstorming-otsou-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to turning raw ideas into cohesive design concepts by clarifying context, identifying requirements, and guiding early design decisions before implementation.

Core Features & Use Cases

  • Guided, question-driven exploration to uncover purpose, constraints, and success criteria.
  • Presentation of 2-3 design approaches with trade-offs to inform decision-making.
  • Incremental design delivery in sections with built-in validation and alignment checks.
  • Generated design documentation and preparation for the next implementation phase.

Quick Start

Start the session by describing the project context and goals, then proceed with one clarifying question at a time, followed by 2-3 design options and a recommended path. After each section, confirm if it looks right and adjust as needed.

Frequently Asked Questions about brainstorming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn raw ideas into cohesive design concepts before implementation?

Structured brainstorming turns raw ideas into cohesive design concepts by clarifying project context, eliciting requirements, and guiding early design decisions. It presents 2-3 design approaches with trade-offs to inform decision-making before implementation.

What is the best way to elicit project requirements during design exploration?

The best way to elicit requirements during design exploration is through guided, question-driven sessions. By enforcing one-question-at-a-time interactions, you systematically uncover project purpose, constraints, and success criteria without overwhelming stakeholders.

How do I validate design decisions incrementally across conversations?

You validate design decisions incrementally by delivering design sections with built-in validation and alignment checks. After presenting 2-3 options and a recommended path, you confirm if the section looks right and adjust as needed before proceeding.

Does structured ideation work for generating design documentation and implementation plans?

Yes, structured ideation works for generating design documentation and implementation plans. The process guides documentation throughout the session and explicitly prepares the validated design concepts for the next implementation phase.

Can I compare multiple design approaches with trade-offs during requirements validation?

Yes, you can compare multiple design approaches because the process explicitly presents 2-3 design options with trade-offs. This comparative validation ensures you evaluate different paths and select a recommended route before finalizing design documentation.