brainstorm

Transform fuzzy ideas into structured specs with clarifying questions and trade-offs.

24|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Borda/.ai-home --skill brainstorm-borda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/Borda/.ai-home/tree/main/.claude/skills/brainstorm
Command: npx skills add https://github.com/Borda/.ai-home --skill brainstorm-borda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn fuzzy ideas into concrete, approved specs before any code is written by guiding clarifying questions, generating multiple approaches with trade-offs, and producing a structured spec for review.

Core Features & Use Cases

  • Interactive clarifying questions that narrow the problem space.
  • Propose 2–3 approaches with clear trade-offs and recommended path.
  • Generate and store a formal spec under docs/specs/ after a self-mentor review.
  • Gate on explicit user approval before any implementation begins.

Quick Start

Provide a fuzzy idea as input to start a brainstorm session and generate the initial spec outline.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn fuzzy ideas into concrete specs before writing code?

To turn fuzzy ideas into concrete specs, you provide your initial concept as input to start a brainstorm session. The skill then guides clarifying questions and proposes multiple approaches with trade-offs to narrow the problem space.

What is the best way to generate a formal spec from an initial product concept?

The best way to generate a formal spec is through a structured brainstorm session that proposes two to three approaches with clear trade-offs. After selecting a path, a self-mentor review identifies gaps before the final spec is stored.

How do I ensure a planning spec covers all edge cases and ambiguities?

To ensure a planning spec covers ambiguities, a self-mentor review process evaluates the generated document for gaps. It only proceeds to final storage under docs/specs/ after explicitly identifying missing details and gating on user approval.

Can I gate implementation on explicit user approval during the ideation phase?

Yes, you can gate implementation on explicit user approval during the ideation phase. The brainstorming process produces a structured spec for review and strictly blocks any downstream implementation until you provide explicit consent.

Does this approach work for governance and planning tasks requiring multiple proposed solutions?

Yes, this approach works for governance and planning tasks by proposing two to three approaches with clear trade-offs and a recommended path. It ensures structured ideation and produces a formal spec for review before any implementation begins.