brainstorming

Name: brainstorming
Availability: InStock
Author: hotriluan

Brainstorm architecture options with trade-off analysis and risk assessments.

2|Updated Dec 24, 2025

Search Tags:#architecture #brainstorming #ideation #feasibility #trade-offs #risk-assessment #design-decision

Ready to run

npx skills add https://github.com/hotriluan/alkana-dashboard --skill brainstorming-hotriluan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming sessions guided by a disciplined framework that yield multiple architecture and feature options with clear trade-offs, risk assessments, and actionable next steps inserted into context.

Core Features & Use Cases

Structured ideation: generate 2-3 viable approaches with pros/cons for architectural, product, or technical decisions.
Honest critique: apply ruthless risk assessment to avoid over-engineering and scope creep.
Decision support: present clear recommendations, justifications, and acceptance criteria for stakeholders.
Collaboration-ready: designed for cross-functional teams including engineers, product, and design for faster alignment.

Quick Start

Provide your objective and constraints, and I will brainstorm 2-3 architectures with trade-off analysis and recommended next steps.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I evaluate trade-offs for software architecture decisions?▼

Evaluating architecture trade-offs involves generating 2-3 viable approaches with risk assessments and clear pros/cons. This structured ideation enforces simplicity and maintainability while delivering actionable recommendations and high-level implementation outlines.

What is the best way to brainstorm features without over-engineering?▼

The best way to brainstorm features without over-engineering is applying ruthless risk assessment during ideation. This delivers 2-3 options with justifications and acceptance criteria, preventing scope creep while ensuring maintainable design decisions.

How do I structure a feasibility assessment for cross-functional teams?▼

Structuring a feasibility assessment for cross-functional teams requires presenting clear recommendations and justifications. This approach aligns engineers, product, and design by evaluating technology options with honest critique and actionable next steps.

Can I use this for technology evaluation and system design?▼

Yes, you can use this for technology evaluation and system design across software projects. By providing your objective and constraints, you receive 2-3 architectures with trade-off analysis, ensuring risk-aware decision making.

When do I need structured ideation for architecture decisions?▼

You need structured ideation for architecture decisions when you require multiple viable approaches with clear trade-offs. It guides technology evaluation and feasibility assessments, ensuring risk-aware decision making and faster alignment.

Why does my brainstorming session lead to scope creep?▼

Brainstorming sessions lead to scope creep without a disciplined framework applying honest critique. Enforcing simplicity and risk-aware decision making delivers 2-3 options with rationale, preventing over-engineering and uncontrolled feature expansion.