brainstorming

Guide teams from vague ideas to concrete designs through structured questioning.

1|Updated Jan 5, 2023
One-click install
npx skills add https://github.com/riez/dots --skill brainstorming-riez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/riez/dots/tree/main/.config/agentic/skills/brainstorming
Command: npx skills add https://github.com/riez/dots --skill brainstorming-riez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming is essential before creating features, components, or modifying behavior. It ensures clear exploration of user intent and requirements, reducing rework and misaligned outcomes by providing a structured process you can use at the start of any project. This Skill enforces a disciplined approach: understanding context, asking focused questions, aligning on success criteria, and guiding teams toward concrete designs before implementation.

Core Features & Use Cases

  • Understand the current project state and goals.
  • Ask one focused, clarifying question at a time to refine ideas.
  • Propose 2-3 design approaches with trade-offs and present a recommended path.
  • Break the design into manageable sections (200-300 words) and validate after each part.
  • Create a documentation plan at docs/plans/YYYY-MM-DD-<topic>-design.md and prepare for implementation.

Quick Start

Begin a guided brainstorming session by describing the project context and asking one clarifying question.

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 concrete designs before implementation?

Structured brainstorming transforms vague ideas by asking focused questions one at a time, proposing 2-3 design approaches with trade-offs, and validating modular sections to ensure clear requirements before implementation begins.

What is the best way to facilitate collaborative ideation across teams for feature planning?

Collaborative ideation succeeds by guiding teams through focused questioning to understand project context, align on success criteria, and validate manageable 200-300 word design sections before proceeding to implementation.

How do I structure a design plan and document the outcomes of a brainstorming session?

Document brainstorming outcomes by creating a design plan at docs/plans/YYYY-MM-DD-<topic>-design.md, capturing the validated modular design sections, recommended approaches, and aligned requirements to prepare directly for implementation.

Can I use this guided questioning approach for early-stage architecture planning?

Yes, guided questioning supports early-stage architecture planning by assessing the current project state, refining requirements through one focused question at a time, and proposing 2-3 concrete design approaches with clear trade-offs for team alignment.

Why do I need a structured brainstorming process for requirements gathering?

A structured brainstorming process for requirements gathering reduces rework and misaligned outcomes by ensuring clear exploration of user intent, aligning on success criteria, and validating concrete designs before any implementation starts.