brainstorming

Guide software design brainstorming through structured review and documentation.

Updated Jun 13, 2026

Search Tags:#software development #project planning #design specification #specification review #collaborative dialogue

Ready to run

npx skills add https://github.com/stu43005/superpowers-codex --skill brainstorming-stu43005

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/stu43005/superpowers-codex/tree/main/skills/brainstorming
Command: npx skills add https://github.com/stu43005/superpowers-codex --skill brainstorming-stu43005

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps to transform ideas into well-defined designs and specifications, ensuring that every project starts with a clear understanding and approval before implementation.

Core Features & Use Cases

Explore Project Context: Understand the current project state through file and document checks.
Ask Clarifying Questions: Refine the idea by asking detailed questions one at a time.
Propose Approaches: Present 2-3 different approaches with trade-offs and recommendations.
Present Design: Break down the design into sections and get user approval after each section.
Write Design Doc: Document the design and commit it to git.
Spec Review Loop: Ensure the spec is structurally complete and design-soundness is approved.

Quick Start

Use the 'brainstorming' skill to explore the project context and refine your idea before proposing a design.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I create a design specification for software development through collaborative dialogue?▼

To create a design specification, you refine project requirements by asking clarifying questions, propose multiple approaches with trade-offs, and document the design for review. This ensures a clear understanding before implementation begins.

What is the best way to brainstorm and propose software design approaches before coding?▼

The best way to brainstorm software design is to explore the project context, ask detailed questions one at a time, and present 2-3 different approaches with trade-offs and recommendations for user approval.

When do I need a structured spec review process for project planning?▼

You need a structured spec review process when starting a new software development project to ensure the design is structurally complete and design-soundness is approved before moving into implementation.

Can I use collaborative dialogue to break down a design and get approval section by section?▼

Yes, you can use collaborative dialogue to break down the design into sections and get user approval after each section. This iterative process helps refine the design specification before final documentation.

How do I document a design and commit it to git for specification review?▼

You document the design by writing a design doc and committing it to git. This is followed by a spec review loop to ensure the specification is structurally complete and design-soundness is approved.

What are the limitations of using structured brainstorming for software design specification?▼

Structured brainstorming requires adherence to a collaborative dialogue and a structured review process, which may slow down rapid prototyping. It focuses on understanding requirements and refining design approaches rather than immediate code generation.