skills.rest
ZaxbyHub
ZaxbyHubOFFICIAL
Explore all skills by this author →
GitHub

brainstorm

Transform fuzzy project requirements into approved specifications through structured guided dialogue.

437|45|Updated Jan 27, 2026
Search Tags:#agent workflow#brainstorm#software planning#requirement gathering#qa gates#spec drafting#discovery dialogue
One-click install
npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill brainstorm-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/brainstorm
Command: npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill brainstorm-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of building the wrong software by resolving ambiguous, unarticulated requirements through structured guided dialogue before any coding or planning begins, preventing costly rework and stakeholder misalignment.

Core Features & Use Cases

  • 7-Phase Strict Discovery Protocol: Enforces ordered execution of context scanning, guided user dialogue, approach evaluation, design outlining, spec drafting with reviewer validation, mandatory QA gate selection, and transition planning to eliminate skipped steps.
  • Optional Domain Research Integration: Supports on-demand 3-agent general council advisory for high-risk or research-heavy projects to provide diverse perspectives for specification decisions.
  • Use Case: Ideal for teams starting a new software feature with vague requirements, ensuring all stakeholders align on scope, approach, and quality guardrails before any implementation work begins.

Quick Start

Invoke the brainstorm skill to run a structured discovery dialogue for your fuzzy project idea, generating a finalized specification and selected QA gate configuration.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
What is structured requirement gathering for fuzzy software ideas?▼

Structured requirement gathering is a guided dialogue process that transforms ambiguous, unarticulated project concepts into clear, approved specifications before coding begins, preventing costly rework and stakeholder misalignment.

How do I draft actionable specs from vague feature requests?▼

You draft actionable specs by engaging in a phased discovery dialogue that sequentially executes context scanning, approach evaluation, design outlining, spec drafting with reviewer validation, and mandatory QA gate selection.

Can I use this discovery dialogue for legacy system refactoring scoping?▼

Yes, this discovery dialogue applies to early-stage software project planning scenarios including new feature ideation and legacy system refactoring scoping where requirements remain exploratory, ambiguous, or not yet formally defined.

What is the best way to evaluate approaches for research-heavy software planning?▼

The best way to evaluate approaches for research-heavy projects is using an on-demand 3-agent general council advisory, which provides diverse perspectives to guide complex specification and design decisions.

Why does software planning require a mandatory QA gate before finalization?▼

Software planning requires a mandatory QA gate to enforce quality guardrails, ensuring all stakeholders align on scope and approach before any implementation work begins and the transition plan is finalized.

Related Skills

Explore More Software Engineering Skills→
AzrinPutraAzrinPutra

intent-capture

Guide exploratory conversations to elicit project requirements and generate an intent brief.

Community
Intermediate
sicktasticsicktastic

brainstorming

Transform vague ideas into structured design plans before implementation.

Community
Advanced
tomlupotomlupo

llm-council

Orchestrates a three-stage council of AI models for structured evaluation and synthesis.

Community
Advanced
magnus919magnus919
40

product-discovery

Map stakeholders, conduct interviews, and distill requirements into formal specifications.

Community
Advanced