brainstorming

Guides collaborative design exploration and produces approved spec documents before implementation.

Updated May 16, 2026
One-click install
npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill brainstorming-michalo1334
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/michalo1334/ScenarioImpactDSL/tree/main/.opencode/skills/brainstorming
Command: npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill brainstorming-michalo1334

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Jumping straight into code without a validated design leads to rework, unexamined assumptions, and misaligned features. This Skill enforces a structured dialogue that turns rough ideas into reviewed, approved design specs before any implementation begins. ## Core Features & Use Cases - Structured Design Dialogue: Explores project context, asks clarifying questions one at a time, proposes 2-3 approaches with trade-offs, and presents the design in sections for incremental approval. - Spec Document Generation: Writes the validated design to docs/superpowers/specs/, runs a self-review for placeholders, contradictions, and ambiguity, then hands off to the writing-plans skill. - Visual Companion: Optionally serves browser-based mockups, diagrams, and A/B layout comparisons via a local WebSocket server, recording user clicks as structured events. - Use Case: Before building a new feature, use this Skill to refine requirements, compare architectural approaches, and produce a committed design document that the user has explicitly approved. ## Quick Start Ask the agent to brainstorm the design for a new feature before writing any code, and answer its clarifying questions one at a time.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I brainstorm a feature design before writing code?▼

Invoke the brainstorming skill before any implementation work. It explores your project context, asks clarifying questions one at a time, proposes 2-3 approaches with trade-offs, and presents a design for your approval before any code is written.

What happens after the design is approved in brainstorming?▼

The design is written to docs/superpowers/specs/ as a dated markdown file and committed to git. After a self-review for placeholders and contradictions plus your review, the skill invokes the writing-plans skill to create the implementation plan.

Does the brainstorming skill work for small or simple changes?▼

Yes, every project goes through the process regardless of perceived simplicity. The design can be just a few sentences for truly simple work, but it must still be presented and approved before implementation begins.

How does the visual companion show mockups in the browser?▼

Run scripts/start-server.sh with your project directory to launch a local server. The agent writes HTML fragments to a watched content directory, the server serves the newest file, and your clicks are recorded as JSON events the agent reads on the next turn.

When should the visual companion not be used?▼

Use the terminal for text-based content like requirements questions, conceptual choices, and tradeoff lists. The browser is only for genuinely visual content such as wireframes, layout comparisons, and architecture diagrams.