brainstorming

Facilitate collaborative brainstorming to create design documents and specifications.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/DevQwiet/my-skills --skill brainstorming-devqwiet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/DevQwiet/my-skills/tree/main/brainstorming
Command: npx skills add https://github.com/DevQwiet/my-skills --skill brainstorming-devqwiet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you turn ideas into fully formed designs and specifications by facilitating collaborative dialogue and ensuring thorough consideration of requirements and constraints before implementation.

Core Features & Use Cases

  • Exploration of Project Context: Analyze existing files, documents, and commits to understand the project's current state.
  • Clarifying Questions: Guide users through a series of questions to refine their ideas and identify requirements.
  • Approach Proposals: Present 2-3 different approaches, with trade-offs and a recommendation.
  • Design Presentation: Break down the design into sections and get user approval before moving on.
  • Documentation: Write a comprehensive design document and commit it to the repository.

Quick Start

Start a brainstorming session by exploring the project context and then proceed to ask clarifying questions. Once the design is agreed upon, write the design document and commit it.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn project ideas into design specifications through collaborative dialogue?

Turning project ideas into design specifications involves analyzing existing files and commits, asking clarifying questions to refine requirements, presenting structured approaches with trade-offs, and getting user approval before documenting the final design.

What is the best way to analyze project context before creating a software design document?

Analyzing project context before creating a software design document requires exploring existing files, documents, and commits to understand the current state, ensuring all requirements and constraints are thoroughly considered before implementation begins.

How do I present different design approaches and trade-offs for requirement analysis?

Presenting design approaches during requirement analysis involves proposing 2-3 different solutions, detailing their specific trade-offs, providing a clear recommendation, and breaking down the chosen design into sections for user approval.

Can I use collaborative brainstorming to refine requirements and write a comprehensive design document?

Yes, collaborative brainstorming refines requirements by guiding users through detailed clarifying questions, exploring project constraints, and securing approval on design sections before writing and committing the comprehensive design document to the repository.

Does this design specification process require any specific dependencies or external tools?

No, this design specification process requires no external dependencies, relying solely on collaborative dialogue, existing project files, and structured documentation to facilitate the brainstorming and requirement analysis workflow.

Why should I use a structured brainstorming session instead of writing specifications directly?

Using a structured brainstorming session instead of writing specifications directly ensures thorough exploration of project context, identifies hidden constraints through clarifying questions, and secures user approval on design approaches before committing final documentation.