brainstorming

Facilitate structured design exploration and document chosen architecture decisions.

33|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/lvlup-sw/exarchos --skill brainstorming-lvlup-sw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/lvlup-sw/exarchos/tree/main/skills-src/brainstorming
Command: npx skills add https://github.com/lvlup-sw/exarchos --skill brainstorming-lvlup-sw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill structures collaborative ideation so teams and agents can explore multiple design and architecture options, avoid premature solutions, and produce a documented, approval-ready design artifact.

Core Features & Use Cases

  • Clarifying Discovery: Guided Phase 1 questioning to surface goals, constraints, existing patterns, and success criteria.
  • Structured Exploration: Phase 2 presents 2-3 genuinely distinct approaches with explicit pros, cons, and a recommended option.
  • Design Documentation & Handoff: Phase 3 produces a numbered requirements-based design saved to the repo and integrates with MCP state, gate checks, and automated chaining to planning.
  • Use Case: Run during feature ideation to converge on a design and produce a traceable design file that downstream planning and implementation can reference.

Quick Start

Ask the agent: let's ideate on a new feature, describe goals and constraints, and present 2-3 approaches with trade-offs and a recommended option.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I explore architecture options for a new feature without committing too early?

To explore architecture options without premature commitment, facilitate a structured ideation process that elicits constraints, asks clarifying questions, and presents 2-3 distinct approaches with explicit trade-offs and a recommended option before documenting the chosen design.

What is the best way to document design decisions for downstream planning?

The best way to document design decisions is to produce a numbered requirements-based design artifact saved to the repo, which integrates with MCP state management and automatically chains to downstream planning workflows when artifacts exist.

How does collaborative ideation work with MCP state integration?

Collaborative ideation with MCP state integration enforces a three-phase process featuring structured questions, numbered acceptance criteria, and adversarial gate checks to ensure the design artifact is approval-ready and traceable.

Can I use structured brainstorming for state management and workflow design?

Yes, you can use structured brainstorming for state management and workflow design by running it during feature ideation to converge on a design, apply adversarial gate checks, and produce a traceable design file for implementation.

What are the limitations of rushing straight into implementation without design exploration?

Skipping design exploration risks premature solutions and untraceable architecture decisions, whereas a structured three-phase ideation process surfaces constraints, evaluates distinct approaches, and enforces gate checks before development begins.