brainstorm

Generate 2-3 viable options with trade-off and risk analysis for software decisions.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/haidonglethqb/CloudSchool --skill brainstorm-haidonglethqb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/haidonglethqb/CloudSchool/tree/main/.claude/skills/brainstorm
Command: npx skills add https://github.com/haidonglethqb/CloudSchool --skill brainstorm-haidonglethqb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming complex software decisions often suffers from scope creep, bias, and poor trade-off visibility. This skill provides a disciplined approach to surface multiple viable options, compare trade-offs, and keep discussions honest.

Core Features & Use Cases

  • Structured ideation with explicit trade-off analysis and risk assessment for architecture, platform choices, and feature design.
  • 2-3 viable options are generated with clear pros, cons, and decision criteria to facilitate fast alignment.
  • Use Case: in a multi-team project, run a session to decide between monolith vs microservices, or evaluate storage strategies with cost/risk profiles.

Quick Start

Provide a topic or challenge and let this skill generate 2–3 actionable options with trade-offs and risk assessments.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I evaluate architecture trade-offs for a software project decision?

To evaluate architecture trade-offs, generate 2-3 viable options with explicit pros, cons, and risk assessments. This structured ideation surfaces decision criteria for fast alignment on complex software design choices.

What is the best way to brainstorm feasibility assessments for software features?

Brainstorming feasibility assessments requires a guided questioning workflow that applies brutal honesty to risk-benefit analysis. This process generates structured outputs suitable for formal decision records.

Can I use structured trade-off analysis to decide between monolith and microservices?

Yes, structured trade-off analysis can decide between monolith and microservices by comparing multiple viable options with clear cost and risk profiles. This facilitates fast alignment in multi-team projects.

How do I prevent bias and scope creep during platform choice brainstorming?

Prevent bias and scope creep during platform choice brainstorming by applying a disciplined approach that surfaces explicit trade-offs. Generating 2-3 options with clear pros and cons keeps discussions honest.

When do I need explicit risk-benefit analysis for design discussions?

You need explicit risk-benefit analysis for design discussions when facing complex software decisions that suffer from poor trade-off visibility. This approach ensures structured outputs suitable for decision records.

What are the limitations of brutal honesty in architecture decision-making?

The limitation of brutal honesty in architecture decision-making is that it requires a guided questioning workflow to function properly. Without structured ideation, the process may not yield clear pros, cons, and decision criteria.