brainstorming

Facilitate structured pre-implementation brainstorming to define requirements and produce a design document.

Updated May 2, 2026

Search Tags:#design #planning #brainstorming #clarification #requirements gathering #user stories

Ready to run

npx skills add https://github.com/iliaal/compound-engineering-plugin --skill brainstorming-iliaal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/iliaal/compound-engineering-plugin/tree/main/plugins/compound-engineering/skills/brainstorming
Command: npx skills add https://github.com/iliaal/compound-engineering-plugin --skill brainstorming-iliaal

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the ambiguity and potential for wasted effort that arises from starting implementation without a clear understanding of requirements, leading to misaligned features and rework.

Core Features & Use Cases

Requirement Clarification: Engages in a structured dialogue to uncover the user's true intent and desired outcomes.
Approach Exploration: Presents and evaluates multiple viable solutions, highlighting pros and cons.
Design Documentation: Captures key decisions and rationale in a standardized format for future reference.
Use Case: Before building a new user authentication flow, this skill can help define whether it should use email/password, OAuth, or a magic link, and document the chosen approach with its trade-offs.

Quick Start

Use the brainstorming skill to explore the requirements for adding a new user profile page.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

What is requirements gathering and how does it clarify ambiguous software features?▼

Requirements gathering is a structured dialogue process used to uncover user intent and desired outcomes before coding, preventing misaligned features and wasted effort by clarifying the what and why of a feature.

How do I explore design decisions for a new user authentication flow?▼

You can explore design decisions by comparing viable solutions like email/password, OAuth, or magic links, evaluating the pros and cons of each approach to determine the optimal path for your software project.

When do I need to document approach trade-offs during project planning?▼

You need to document approach trade-offs during project planning when defining initial project requirements, ensuring that key design decisions and their rationale are captured in a standardized format for future reference.

How to write user stories from brainstorming sessions before implementation?▼

Writing user stories from brainstorming sessions involves applying structured questioning to clarify ambiguous user needs and translating those defined requirements into actionable development tasks.

What's the best way to define software requirements before starting implementation?▼

The best way to define software requirements is through pre-implementation brainstorming that compares multiple viable solutions and highlights their pros and cons to produce a comprehensive design document.

Why does starting implementation without design documentation lead to rework?▼

Starting implementation without design documentation leads to rework because it arises from ambiguity and a lack of clear understanding of requirements, resulting in misaligned features and wasted effort.