brainstorm

Guides structured discovery dialogue, approach selection, and spec drafting through seven ordered phases.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill brainstorm-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.opencode/skills/brainstorm
Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill brainstorm-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning fuzzy, exploratory ideas into a concrete, reviewable specification is hard without structure. This Skill enforces a disciplined seven-phase brainstorm protocol that draws requirements out through dialogue before any spec is committed. ## Core Features & Use Cases - Structured Discovery Dialogue: Asks one focused question at a time with informed defaults, capped at six questions, to collapse uncertainty efficiently. - Approach Comparison & Design: Produces 2-4 candidate approaches with tradeoffs and risks, then drafts named design sections covering data models, components, and failure modes. - Spec Writing with Review Gate: Generates a WHAT/WHY-only spec with FR/SC numbering, clarification markers, and an independent reviewer pass before finalization. - QA Gate Selection: Presents eleven configurable quality gates (reviewer, test engineer, SAST, drift check, and more) for explicit user election before planning. - Use Case: A developer says "let's think through adding multi-tenant support" — the Skill scans the codebase, asks targeted questions, compares architectures, and produces a reviewed spec ready for planning. ## Quick Start Ask the architect to brainstorm your feature idea, for example by saying "brainstorm how we should add real-time notifications to the app".

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn a vague feature idea into a written spec?▼

Invoke the brainstorm mode with your topic. It runs a context scan of the codebase, asks up to six focused questions with defaults, presents candidate approaches, and drafts a reviewed spec file with numbered requirements and scenarios.

When should I use brainstorm mode instead of writing a spec directly?▼

Use brainstorm when requirements are fuzzy or exploratory and need to be drawn out through dialogue. If you already have clear, articulated requirements, go straight to specify mode instead.

How many questions does the brainstorm dialogue ask?▼

The dialogue phase asks exactly one focused question per message, with a hard cap of six questions total. Each question includes why it matters, the default that will be used, and the options being weighed.

Can the brainstorm spec include technology stack details?▼

No. The spec follows WHAT/WHY-only content rules with no tech stack or implementation details. Technology-aware design notes live in separately named design sections that the spec cross-references.

What QA gates can be enabled after brainstorming?▼

Eleven gates are presented for user selection, including reviewer, test engineer, SAST scanning, drift check, council modes, hallucination guard, and mutation testing. Defaults are pre-stated and the user explicitly accepts or customizes them.