sl:brainstorm

Brainstorm structured ideas and trade-off analyses for architecture decisions.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/HuynhHoangPhuc/solon --skill sl-brainstorm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sl:brainstorm
Source: https://github.com/HuynhHoangPhuc/solon/tree/main/plugins/solon-core/skills/brainstorm
Command: npx skills add https://github.com/HuynhHoangPhuc/solon --skill sl-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming with research delegation and structured debate to generate well-reasoned solutions quickly.

Core Features & Use Cases

  • Phase-based brainstorming workflow: Scout → Discovery → Research → Analysis → Debate → Documentation → Finalize.
  • Delegated research via agents and structured debate to surface trade-offs and constraints.
  • Generate implementation-ready decisions and stakeholder-facing documentation.

Quick Start

Initiate a brainstorm session on the given topic and generate a structured report with trade-offs.

Frequently Asked Questions about sl:brainstorm

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

FAQPage Schema
How do I structure a brainstorming session for software architecture decisions?

Structured brainstorming for architecture decisions follows a phase-based workflow from Scout to Finalize, using delegated research and debate to surface trade-offs. This generates implementation-ready documentation and reasoned solutions quickly.

What is the best way to analyze trade-offs during feature exploration?

Trade-off analysis during feature exploration uses a structured debate phase to evaluate constraints and feasibility. Delegated research agents surface competing factors, enabling debate-driven decision making for implementation-ready outcomes.

Can I use this for feasibility studies and multi-phase ideation workflows?

Feasibility studies and multi-phase ideation workflows are supported through a structured pipeline spanning Discovery, Research, Analysis, and Documentation. This process delegates research tasks to agents to satisfy complex workflow requirements.

How does debate-driven decision making work for software projects?

Debate-driven decision making for software projects uses structured phases to research and analyze constraints, then debates the findings. This surfaces architectural trade-offs and generates stakeholder-facing documentation for final decisions.

Does this ideation process require any specific dependencies or components?

This ideation process requires no external dependencies or components to operate. It self-contains the multi-phase workflow, research delegation, and documentation generation internally to produce implementation-ready architectural decisions.