brainstorming

Name: brainstorming
Availability: InStock
Author: merlyn-huntress

Guide structured brainstorming to clarify requirements and capture design decisions.

Updated Feb 26, 2026

Search Tags:#design #planning #brainstorming #requirements #clarification #approach exploration

Ready to run

npx skills add https://github.com/merlyn-huntress/compound-engineering-plugin-no-mcp --skill brainstorming-merlyn-huntress

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps clarify user intent, explore different approaches, and define design decisions before starting the implementation phase, preventing wasted effort on misunderstood requirements.

Core Features & Use Cases

Requirement Clarification: Asks targeted questions to uncover the core purpose, users, constraints, and success criteria of a feature.
Approach Exploration: Proposes and evaluates 2-3 distinct implementation strategies, outlining their pros and cons.
Design Summarization: Captures key decisions and open questions in a structured document for easy handoff to planning.
Use Case: Before building a new user authentication flow, this skill can help determine whether to use email/password, OAuth, or a combination, and document the chosen approach.

Quick Start

Use the brainstorming skill to help me think through the requirements for a new user profile page.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I clarify software requirements before starting implementation?▼

Clarify software requirements by using a structured brainstorming process that asks targeted questions to uncover core purpose, users, constraints, and success criteria. This prevents wasted effort on misunderstood project features before you build.

What is the best way to explore different implementation approaches for a new feature?▼

Exploring implementation approaches is best done by proposing and evaluating 2-3 distinct strategies, outlining their pros and cons. This helps you evaluate potential solutions and choose the optimal design path for your software development project.

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

Document design decisions by capturing key choices and open questions in a structured summarization document. This provides easy handoff to planning and ensures your chosen authentication approach is recorded for future reference.

When should I use a structured brainstorming process for software development?▼

Use a structured brainstorming process when you need to define design decisions before implementation, preventing wasted effort. It supports iterative validation and adherence to YAGNI principles for features like new user profile pages.

Does this approach exploration support iterative validation of project requirements?▼

Yes, approach exploration supports iterative validation by guiding users through understanding intent and capturing design decisions. It ensures project requirements are continuously refined and validated against YAGNI principles during brainstorming.

Why does requirement clarification prevent wasted effort in software engineering?▼

Requirement clarification prevents wasted effort by uncovering the true core purpose and constraints of a feature before coding begins. It ensures you only build what is needed, adhering to YAGNI principles and avoiding misunderstood requirements.