brainstorming

Guide structured brainstorming with a 4-step framework and Socratic questioning.

1|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/gaoqiongxie/skills-ai --skill brainstorming-gaoqiongxie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/gaoqiongxie/skills-ai/tree/main/brainstorming
Command: npx skills add https://github.com/gaoqiongxie/skills-ai --skill brainstorming-gaoqiongxie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the high cost of rework and subpar design decisions that stem from rushing into coding before fully clarifying requirements, identifying constraints, and anticipating edge cases.

Core Features & Use Cases

  • 4-Step Structured Method: Guides users through clarifying core problems, identifying constraints, enumerating edge cases, and generating evaluated alternative solutions for any development task.
  • Socratic Questioning Framework: Provides targeted questions to uncover hidden requirements, tradeoffs, and risks that are often missed in initial planning.
  • Ready-to-Use Templates: Includes pre-built templates for feature development, bug fix planning, and architecture design to standardize output.
  • Use Case Example: Use it when designing a new payment system to identify constraints like PCI compliance, edge cases like failed transaction retries, and compare monolithic vs microservice architecture options before writing any code.

Quick Start

Use the brainstorming skill to apply the 4-step method to your new team collaboration feature, including identifying time constraints of a 2-week sprint and edge cases like concurrent edit conflicts.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I prevent rework when planning new software features?

Prevent rework by applying structured brainstorming before coding to fully analyze requirements, identify constraints, and anticipate edge cases. This approach uses Socratic questioning to uncover hidden risks and tradeoffs early in the development cycle.

What is the best way to analyze requirements for a complex architecture design?

Analyzing requirements for architecture design is best done using a 4-step structured method that clarifies core problems, identifies constraints, enumerates edge cases, and evaluates alternative solutions like monolithic versus microservice options before development.

How do I identify edge cases and constraints before starting technical planning?

Identify edge cases and constraints during technical planning by applying a Socratic questioning framework. It provides targeted questions to uncover hidden requirements, tradeoffs, and risks often missed in initial feature planning and bug root cause analysis.

Can I use structured brainstorming for bug root cause analysis and refactoring planning?

Yes, you can use structured brainstorming for bug root cause analysis and refactoring planning. It applies a standardized 4-step output framework to evaluate constraints and generate actionable, well-considered development plans for these software workflows.

Does this requirement analysis method work for tight sprint schedules?

Yes, this requirement analysis method works for tight sprint schedules by clarifying time constraints alongside edge cases like concurrent edit conflicts. It delivers ready-to-use templates for feature development to standardize output and accelerate planning.

When should I not rush into coding without feature planning?

You should not rush into coding without feature planning when designing complex systems like a new payment system. Without structured brainstorming, you risk costly rework from missing constraints like PCI compliance or unhandled edge cases like failed transaction retries.