brainstorm

Facilitate structured brainstorming and trade-off analysis for software engineering decisions.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/IoT-VN/tuya-energy-dashboard --skill brainstorm-iot-vn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/IoT-VN/tuya-energy-dashboard/tree/main/.opencode/skills/brainstorm
Command: npx skills add https://github.com/IoT-VN/tuya-energy-dashboard --skill brainstorm-iot-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users make better technical and architectural decisions by facilitating structured brainstorming, challenging assumptions, and providing honest trade-off analyses.

Core Features & Use Cases

  • Ideation & Exploration: Generate and evaluate multiple solutions for complex problems.
  • Decision Support: Provide data-driven recommendations for architecture, features, and technical debt.
  • Risk Assessment: Identify potential pitfalls and mitigation strategies early in the development cycle.
  • Use Case: When deciding between two different database technologies for a new feature, this Skill can help weigh the pros and cons of each based on scalability, cost, and team familiarity.

Quick Start

Use the brainstorm skill to explore solutions for improving the performance of the user authentication module.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I evaluate technical trade-offs when choosing between different architecture patterns?

Structured brainstorming evaluates technical trade-offs by challenging assumptions and analyzing alternatives for system architecture. It provides data-driven recommendations by applying principles like YAGNI, KISS, and DRY to ensure optimal, maintainable outcomes.

What is the best way to facilitate a technical debate over feature design and feasibility?

Facilitating a technical debate requires exploring alternative solutions and assessing risks for feature design and feasibility. This process identifies potential pitfalls and mitigation strategies early, ensuring honest trade-off analyses for complex software engineering challenges.

How do I brainstorm alternative solutions for resolving technical debt?

Brainstorming alternative solutions for technical debt involves generating multiple options and evaluating trade-offs based on scalability, cost, and team familiarity. It provides decision support to prioritize mitigation strategies that yield maintainable software engineering outcomes.

When do I need to use structured ideation for system architecture decisions?

Structured ideation is needed for system architecture decisions when facing complex problems that require deep trade-off analysis and risk assessment. It helps weigh pros and cons of different technologies to prevent early design pitfalls and ensure maintainability.

Does this approach to decision making work for evaluating different database technologies?

Decision making works for evaluating database technologies by analyzing trade-offs based on scalability, cost, and team familiarity. It challenges existing assumptions to provide honest, data-driven recommendations for selecting the optimal technology.

What are the limitations of using structured brainstorming for software engineering challenges?

Limitations of structured brainstorming include its dependence on the quality of input assumptions and the inherent complexity of quantifying team familiarity. It guides technical debates but requires clear constraints to effectively apply KISS and YAGNI principles.