brainstorming

mgkyawzayya's avatarfrom mgkyawzayya

Brainstorm and advise on technical decisions using structured process. EXCLUSIVE to brainstormer agent. Does NOT implement — only advises.

⭐1stars🔀0forks📁View on GitHub🕐Updated Dec 14, 2025
[Architecture Design]

When & Why to Use This Skill

The Brainstorming skill is a specialized framework designed for Claude agents to facilitate high-level technical decision-making and architectural planning. It utilizes a structured six-step process—Discover, Research, Analyze, Debate, Consensus, and Document—to help engineering teams evaluate complex trade-offs. By leveraging proven frameworks like SCAMPER and Weighted Criteria analysis, this skill ensures that technical choices are data-driven, risk-aware, and aligned with project constraints before any code is implemented.

Use Cases

  • Architectural Trade-off Analysis: Systematically compare multiple technical approaches (e.g., Microservices vs. Monolith) by evaluating pros, cons, and feasibility weights.
  • Technical Discovery & Requirement Gathering: Conduct deep-dive research into existing codebases and external documentation to identify constraints and dependencies for new features.
  • Creative System Optimization: Apply the SCAMPER framework to rethink legacy components, identifying opportunities to substitute, combine, or eliminate parts of the stack for better performance.
  • Strategic Decision Documentation: Generate comprehensive reports that outline recommended solutions, risk mitigation strategies, and success metrics to ensure stakeholder alignment.
namebrainstorming
descriptionBrainstorm and advise on technical decisions using structured process. EXCLUSIVE to brainstormer agent. Does NOT implement — only advises.
allowed-toolsRead, Grep, Glob, Bash, WebFetch

Brainstorming

Exclusive to: brainstormer agent

⚠️ CRITICAL: This skill is for brainstorming and advising ONLY. Do NOT implement solutions.

Instructions

  1. Discover — Ask clarifying questions about requirements, constraints, timeline
  2. Research — Gather information from codebase and external sources
  3. Analyze — Evaluate multiple approaches with pros/cons
  4. Debate — Present options, challenge assumptions, find optimal solution
  5. Consensus — Ensure alignment on chosen approach
  6. Document — Create comprehensive summary report

Output Template

# Brainstorm Summary: [Topic]

## Problem Statement
[Description]

### Requirements
- [Requirement]

### Constraints
- [Constraint]

## Evaluated Approaches

### Option A: [Name]
| Pros | Cons |
|------|------|
| [Pro] | [Con] |

### Option B: [Name]
[Same structure]

## Recommended Solution
[Decision and rationale]

## Risks & Mitigations
| Risk | Impact | Mitigation |
|------|--------|------------|

## Success Metrics
- [ ] [Metric]

## Next Steps
1. [Step] — [Owner]

Decision Frameworks

Weighted Criteria

Criteria Weight
Feasibility 30%
Maintainability 25%
Performance 20%
Time to build 25%

SCAMPER

  • Substitute — What can be replaced?
  • Combine — What can be merged?
  • Adapt — What can we borrow?
  • Modify — What can change?
  • Put to other uses — New applications?
  • Eliminate — What can be removed?
  • Reverse — What if opposite?

Examples

  • "Brainstorm architecture for feature X"
  • "Compare these two technical approaches"
  • "Help me decide between options"