brainstorm

Guide structured ideation to produce a design document with implementation plan.

Updated Aug 27, 2026

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

Ready to run

npx skills add https://github.com/bketelsen/ytsejam --skill brainstorm-bketelsen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/bketelsen/ytsejam/tree/main/contrib/skills/brainstorm
Command: npx skills add https://github.com/bketelsen/ytsejam --skill brainstorm-bketelsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative brainstorming is often unfocused without a structured process. This skill provides a guided approach to explore project context, ask clarifying questions, generate 2-3 design approaches, and produce a design document before implementation.

Core Features & Use Cases

Explore project context, cog memory, wiki references, and recent activity to inform design.
Ask clarifying questions one at a time to refine requirements.
Propose 2-3 approaches with trade-offs; present a recommended option.
Present design sections and obtain user approvals before moving to implementation; write the canonical design doc and transition to the write-plan stage.

Quick Start

Begin a brainstorming session to transform a raw idea into a documented design plan.

Frequently Asked Questions about brainstorm

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

FAQPage Schema

How do I turn raw product ideas into a concrete design document collaboratively?▼

Structured ideation converts raw ideas into concrete designs by guiding a team through context exploration, clarifying questions, and approach generation to produce a final design doc. The process enforces guardrails and obtains approvals before implementation.

What is the best way to facilitate structured brainstorming for software architecture decisions?▼

Structured brainstorming for software architecture decisions works by exploring project context and recent activity, asking clarifying questions iteratively, and proposing 2-3 design approaches with trade-offs. A recommended option is presented and documented before implementation begins.

How do I create a design doc with multiple approaches and trade-offs before implementation?▼

Design doc creation follows a guided process of generating 2-3 approaches with trade-offs, presenting design sections for user approval, and writing the canonical design document to the repo with an implementation plan. This ensures requirements are refined before any code is written.

Can I use collaborative ideation for early-stage product features without losing focus?▼

Collaborative ideation for early-stage product features maintains focus by enforcing structured process steps and guardrails. It explores project context, wiki references, and asks clarifying questions one at a time to refine requirements before proposing approaches.

Does structured brainstorming require any specific dependencies or components to run?▼

Structured brainstorming requires no external dependencies or components to run. It operates independently to guide teams through ideation, design approach generation, and design document creation without needing additional packages or modules installed.

When should I not use a guided brainstorming process for design decisions?▼

Guided brainstorming for design decisions may be unnecessary when requirements are already fully specified or the scope is too small to warrant 2-3 trade-off approaches. The process enforces iterative questioning and approval steps that add overhead for straightforward implementation tasks.