brainstorm

Brainstorm software architecture options with pros, cons, and markdown summaries.

7|3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill brainstorm-brainbrewlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/brainbrewlabs/brainbrew-devkit/tree/main/.claude/skills/brainstorm
Command: npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill brainstorm-brainbrewlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps product and engineering teams quickly explore viable technical solutions, trade-offs, and implementation paths for proposed features without committing to code or plans prematurely. It reduces wasted effort on unrealistic designs by forcing feasibility checks, concise trade-off analysis, and stakeholder-aligned recommendations.

Core Features & Use Cases

  • Clarifying discovery: Asks probing questions to uncover constraints, success metrics, timelines, and hidden assumptions before proposing solutions.
  • Multi-option analysis: Presents 2-3 distinct approaches for architecture, UX, or implementation with clear pros, cons, and risk assessments.
  • Decision-ready output: Produces a concise markdown summary report with recommended path, implementation considerations, risks, and success metrics.
  • Use Case: Use this skill to compare approaches for scaling an authentication system, weigh cost vs. latency trade-offs for a new search feature, or prioritize MVP scope for a mobile release.

Quick Start

Ask the brainstorm skill a focused product/technical question such as How should I design a scalable signup flow for 100k monthly users?

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I analyze technical trade-offs for a new software feature?

To analyze technical trade-offs, the skill evaluates 2-3 distinct architectural approaches, weighing pros, cons, and risks against your constraints. It forces feasibility checks and stakeholder alignment to prevent wasted effort on unrealistic designs.

What is the best way to compare system architecture design alternatives before writing code?

Comparing system architecture alternatives requires iterative clarification of success metrics and timelines before proposing solutions. This skill generates multiple design paths with explicit pros, cons, and risk assessments without committing to code prematurely.

How do I scope MVP features and validate feasibility for a mobile release?

Scoping MVP features requires probing questions to uncover hidden assumptions and constraints before proposing solutions. The skill validates feasibility and prioritizes scope, producing a concise markdown summary with recommended paths and implementation considerations.

Does this brainstorming approach work for both backend and frontend engineering decisions?

Yes, this brainstorming approach works for backend, frontend, and UX engineering decisions. It applies to early-stage feature scoping, technical trade-off analysis, and design alternatives across the full product stack.

When should I not use an automated system architecture trade-off analysis?

You should avoid automated trade-off analysis if your feature requires no multiple solution proposals or lacks defined success metrics. The process relies on iterative clarification and explicit risk assessments to deliver decision-ready output.