brainstorm

Generate design options with pros and cons for architecture decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorms architecture and design ideas with brutal honesty to surface trade-offs, risks, and feasible paths early, reducing rework and misalignment.

Core Features & Use Cases

  • Brutal honesty ideation to surface assumptions, risks, and constraints
  • Generate 2-3 viable design options with clear pros/cons
  • Facilitate stakeholder alignment and decision logging on architectural trade-offs

Quick Start

Provide 2-3 alternative design options with pros and cons for the given problem.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I brainstorm architecture design options with clear trade-offs?

Generate 2-3 alternative design options with clear pros and cons for your problem to evaluate feasibility. This approach surfaces assumptions, risks, and constraints early, providing actionable insights for technology selection and reducing rework before implementation.

How does brutal honesty ideation work for system design feasibility analysis?

This ideation process generates 2-3 viable design options with articulated alternatives, guardrails, and success criteria. It surfaces hidden assumptions and constraints early, ensuring decision documentation captures realistic architectural trade-offs for stakeholder alignment.

Can I use this for technology selection and risk assessment across product scopes?

Yes, this applies to technology selection and risk assessment across product scopes from high-level architecture to implementation details. It evaluates feasibility by mapping design decisions against guardrails and success criteria for structured exploration.

What is the best way to document architectural decisions and stakeholder alignment?

Log architectural trade-offs during the ideation of 2-3 viable design options with clear pros and cons. Clearly articulating alternatives, guardrails, and success criteria captures the rationale behind design decisions, facilitating stakeholder alignment.

When should I not use brutal honesty ideation for architecture trade-offs?

Avoid brutal honesty ideation when your problem requires a single deterministic solution rather than structured exploration of alternatives. It generates 2-3 design options to surface risks and trade-offs, which adds unnecessary analysis overhead for simple implementation details lacking architectural complexity.