brainstorming

Converts vague ideas into structured design concepts and requirements.

Updated Jan 12, 2021

Search Tags:#design #brainstorming #collaboration #ideation #requirements #product-management #design-doc

Ready to run

npx skills add https://github.com/jssee/.dotfiles --skill brainstorming-jssee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/jssee/.dotfiles/tree/main/.config/opencode/skill/brainstorming
Command: npx skills add https://github.com/jssee/.dotfiles --skill brainstorming-jssee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert vague ideas into structured design concepts and actionable requirements by guiding a focused brainstorming process that clarifies intent, constraints, and success criteria.

Core Features & Use Cases

Structured inquiry: gather project context through a single-question-at-a-time dialogue.
Option exploration: present 2-3 viable design approaches with trade-offs.
Incremental design: present the design in 200-300 word sections with validation prompts after each.
Documentation handoff: generate a design doc and tasks for implementation when proceeding.

Quick Start

Start by asking one clarifying question to establish the project context.
Produce a staged design outline in 200-300 word sections, each followed by a confirmation prompt.
After finalizing, write the validated design to docs/designs/YYYY-MM-DD-<topic>.md and prepare implementation tickets if needed.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I convert vague product ideas into structured design concepts and requirements?▼

Structured brainstorming converts vague ideas into design concepts by gathering project context through single-question-at-a-time dialogue, mapping constraints, and exploring viable design approaches with clear trade-offs to establish actionable requirements.

What is the best way to explore design options during early-stage product discovery?▼

The best way to explore design options during product discovery is to generate 2-3 viable approaches with explicit trade-offs. This allows teams to evaluate decision criteria against mapped constraints before committing to an incremental design path.

How do I generate a design doc and implementation tickets from a planning session?▼

Generate a design doc and implementation tickets by validating incremental design sections step-by-step. Once finalized, the process automatically writes the validated design to a dated markdown file and prepares actionable implementation tasks for handoff.

Can I use incremental design delivery for feature ideation across multiple projects?▼

Yes, you can use incremental design delivery for feature ideation across multiple projects. It presents design concepts in 200-300 word sections with validation prompts, ensuring disciplined reasoning and clear documentation across different project contexts.

Does structured brainstorming work for design reviews and early-stage feature planning?▼

Yes, structured brainstorming works effectively for design reviews and early-stage feature planning. It applies focused inquiry to context gathering and option exploration, guiding teams through constraint mapping to produce organized design sections and actionable next steps.