brainstorming

Clarify goals and requirements through guided one-question-at-a-time discussions.

1|Updated Apr 13, 2015
One-click install
npx skills add https://github.com/tyler-dot-earth/.dotfiles --skill brainstorming-tyler-dot-earth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/tyler-dot-earth/.dotfiles/tree/main/agents/skills/brainstorming
Command: npx skills add https://github.com/tyler-dot-earth/.dotfiles --skill brainstorming-tyler-dot-earth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming provides a structured, collaborative approach to understand user intent and clarify requirements before design or implementation, reducing rework and misalignment.

Core Features & Use Cases

  • Understanding context: Assess project state, stakeholders, and constraints before proposing solutions.
  • Guided questioning: One focused question at a time to refine ideas and avoid scope creep.
  • Design framing: Generate 2-3 design approaches with trade-offs and recommended path.
  • Documentation handoff: Produce a clear plan and sections for subsequent implementation or review.

Quick Start

Start a collaborative brainstorming session by clarifying goals and asking one focused question at a time.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I facilitate a brainstorming session to align cross-functional teams before design?▼

Brainstorming sessions align cross-functional teams by assessing project context and constraints first, then guiding one-question-at-a-time discussions to clarify requirements and prevent scope creep before design begins.

What is the best way to frame product discovery and generate design approaches?▼

Framing product discovery involves clarifying goals and refining ideas through focused questioning, ultimately producing 2-3 actionable design approaches with documented trade-offs and a recommended path forward.

Can I use structured ideation to reduce misalignment and rework during feature planning?▼

Structured ideation reduces rework and misalignment by documenting decisions and understanding user intent early. It guides focused discussions to validate requirements before implementation begins.

How do I document decisions and hand off requirements after a design framing session?▼

Document decisions during design framing by capturing one-question-at-a-time discussions and validated goals, producing a clear plan with defined sections for subsequent implementation and review handoff.

When should I avoid collaborative brainstorming for feature ideation?▼

Avoid collaborative brainstorming when project context is already well-defined, stakeholders are fully aligned on requirements, or constraints leave no room to evaluate multiple design approaches with trade-offs.