brainstorm

Explores a codebase and produces an approved design specification before implementation begins.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill brainstorm-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/greglas75/zuvo/tree/main/skills/brainstorm
Command: npx skills add https://github.com/greglas75/zuvo --skill brainstorm-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into coding a new feature without understanding the existing codebase, edge cases, or failure modes, which leads to rework and misaligned implementations. This Skill enforces a design-first workflow that produces a reviewed, approved specification document before any code is written. ## Core Features & Use Cases - Parallel codebase exploration: Dispatches Code Explorer, Domain Researcher, and Business Analyst agents to map modules, research libraries, and surface edge cases and failure modes. - Structured design dialogue: Asks clarifying questions, presents 2-3 named approaches with trade-offs, and walks the user through section-by-section approval. - Spec generation with acceptance proofs: Writes a dated spec to docs/specs/ containing data model, API surface, failure-mode tables, acceptance criteria with proof procedures, rollback strategy, and backward compatibility notes. - Use Case: When asked to add a notification system to an existing app, the Skill analyzes the current services, researches delivery libraries, identifies concurrency edge cases, and produces an approved spec that downstream plan and execute skills implement. ## Quick Start Ask the agent to brainstorm a design spec for the new feature you want to build before writing any code.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I create a design spec before writing code?

Invoke the brainstorm workflow with your feature request. It dispatches code exploration, domain research, and business analysis agents, asks clarifying questions, presents design approaches with trade-offs, and writes an approved spec to docs/specs/ for downstream planning.

What agents does the brainstorm workflow dispatch?

It dispatches three parallel agents: a Code Explorer that maps modules and blast radius, a Domain Researcher that investigates libraries and prior art, and a Business Analyst that identifies edge cases, failure modes, and acceptance criteria.

Can I skip the design phase and start coding immediately?

No. The skill enforces a hard gate that blocks implementation code until the spec is approved. Implementation is handled later by separate plan and execute skills that consume the approved spec by its spec_id.

Does the brainstorm skill work in non-interactive environments like Cursor?

Yes. In async environments it skips clarifying questions, annotates decisions as [AUTO-DECISION] with rationale, produces the full spec in one pass, and sets status to Reviewed so the user explicitly approves afterward.

What happens if an exploration agent fails during brainstorming?

A failed required agent is retried once; if it still fails, the spec is marked Draft with the gap noted and never auto-approved. If two or more required agents fail, the workflow stops and asks the user how to proceed.