brainstorming

Clarifies software feature requirements and explores implementation approaches with trade-offs before planning.

49|4|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/gvkhosla/compound-engineering-pi --skill brainstorming-gvkhosla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/gvkhosla/compound-engineering-pi/tree/main/plugins/compound-engineering/skills/brainstorming
Command: npx skills add https://github.com/gvkhosla/compound-engineering-pi --skill brainstorming-gvkhosla

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 or poorly scoped features.

Core Features & Use Cases

  • Requirement Clarification: Guides users through a series of questions to define the purpose, users, constraints, and success criteria of a feature.
  • Approach Exploration: Proposes and evaluates 2-3 distinct implementation strategies, outlining their pros, cons, and best-fit scenarios.
  • Design Summarization: Captures key decisions and open questions in a structured document for easy handoff to the planning phase.
  • Use Case: Before building a new user notification system, this skill can help determine if it should be email-only, in-app, or both, and explore different technical approaches for sending those notifications.

Quick Start

Use the brainstorming skill to explore approaches for building a user profile editing feature.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I clarify feature requirements before starting software implementation?

To clarify feature requirements, you can use a structured brainstorming process that guides you through defining the purpose, users, constraints, and success criteria, ensuring clarity before planning begins.

What is the best way to explore multiple solution approaches for a new software feature?

The best way to explore solution approaches is to evaluate 2-3 distinct implementation strategies, outlining their pros, cons, and best-fit scenarios to inform your design decisions.

How do I document design decisions for a user notification system?

You document design decisions by capturing key choices and open questions in a structured summary document, which ensures easy handoff to the planning phase.

Can I use this to avoid anti-patterns during pre-implementation feature exploration?

Yes, you can use this to avoid anti-patterns during feature exploration by supporting iterative validation and ensuring design clarity before moving into the implementation phase.

Does this brainstorming process work for defining technical approaches like email versus in-app notifications?

Yes, this brainstorming process works for defining technical approaches by helping you determine if features should be email-only, in-app, or both, and exploring different technical trade-offs.