brainstorming

Facilitate brainstorming sessions to produce design-ready specifications.

582|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/shobcoder/shob --skill brainstorming-shobcoder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/shobcoder/shob/tree/main/skills/brainstorming
Command: npx skills add https://github.com/shobcoder/shob --skill brainstorming-shobcoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming sessions often stall without a structured approach to understand context, ask clarifying questions, evaluate options, and produce a clear design plan before implementation.

Core Features & Use Cases

  • Structured inquiry: guides the team from context discovery to design validation.
  • Multi-approach evaluation: presents 2-3 design options with trade-offs.
  • Design-first workflow: ensures user-approved designs before coding.

Quick Start

Begin by clarifying the project goal, gathering context, and drafting a concise design plan for approval.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn vague product ideas into actionable design requirements?

To turn vague ideas into actionable design requirements, use structured brainstorming sessions that guide context discovery, ask clarifying questions, and evaluate multiple design approaches with trade-offs before producing a design-ready specification.

What is the best way to evaluate design approaches before coding?

Evaluating design approaches before coding requires presenting 2-3 design options with clear trade-offs. This multi-approach evaluation ensures teams achieve design alignment and user approval prior to any implementation.

How do I structure a brainstorming session for product discovery?

Structuring a brainstorming session for product discovery involves guiding the team through context discovery, structured inquiry, and design validation to ensure a concise design plan is drafted for approval.

Do I need a design doc to start coding a new feature?

A design doc is needed to start coding because a design-first workflow ensures user-approved designs are finalized first. Structured inquiry and exploration of approaches satisfy this requirement before implementation begins.

Can I use this brainstorming approach for any product context?

You can use this brainstorming approach across product contexts where discovery, clarifying questions, and design alignment are required before implementation, ensuring broad applicability for transforming ideas into specifications.