brainstorming

Compare software architecture options with trade-offs and acceptance criteria.

Updated Dec 11, 2025

Search Tags:#architecture #brainstorming #ideation #trade-offs #risk-analysis #design-discussion

Ready to run

npx skills add https://github.com/hoanghd218/bandoxaynha.ai --skill brainstorming-hoanghd218

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/hoanghd218/bandoxaynha.ai/tree/main/.opencode/skill/brainstorming
Command: npx skills add https://github.com/hoanghd218/bandoxaynha.ai --skill brainstorming-hoanghd218

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative brainstorming with brutal honesty to generate architecture options, identify trade-offs, and surface risks early in the design process.

Core Features & Use Cases

Multi-approach analysis for architecture decisions, technology choices, and system interactions.
Principle-driven recommendations that balance simplicity, scalability, and maintainability.
Structured debate and risk assessment to surface edge cases and feasibility concerns.
Use Case: clients explore 2-3 high-level designs and compare trade-offs before committing to implementation.

Quick Start

Provide a candid, multi-scenario brainstorm for a given system, outlining at least two viable architectures with trade-offs and next steps.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I compare architecture options and identify trade-offs during system design?▼

To compare architecture options, you need a structured brainstorming approach that evaluates multiple viable designs against constraints, surfacing trade-offs and risks early before committing to implementation.

What is the best way to brainstorm software architecture without overengineering the design?▼

The best way to brainstorm architecture without overengineering is applying brutal honesty and structured questioning to generate principle-driven recommendations, balancing simplicity and maintainability while defining actionable acceptance criteria.

How do I conduct a risk assessment for technology choices in a software system?▼

Conducting a risk assessment for technology choices requires structured debate across diverse scenarios to surface edge cases, feasibility concerns, and constraints, ensuring maintainability and performance are maximized.

Can I use principled ideation to explore multiple high-level designs for clients?▼

Yes, you can use principled ideation to explore 2-3 high-level designs for clients, comparing trade-offs and outlining next steps to guide design decisions before implementation begins.

When do I need structured questioning for architecture decisions?▼

You need structured questioning for architecture decisions when you must surface hidden constraints, evaluate alternative approaches across diverse scenarios, and describe actionable decisions without overengineering the system.

What are the limitations of brutal honesty in design discussions?▼

The limitation of brutal honesty in design discussions is that it focuses strictly on feasibility, risks, and constraints, which may bypass subjective client preferences or creative, non-technical design aesthetics.