brainstorm

Generates technical design docs with weighed approaches from rough implementation ideas.

3|Updated Oct 28, 2020
One-click install
npx skills add https://github.com/k0d3x8its/dotfiles --skill brainstorm-k0d3x8its
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/k0d3x8its/dotfiles/tree/main/claude/.claude/skills/brainstorm
Command: npx skills add https://github.com/k0d3x8its/dotfiles --skill brainstorm-k0d3x8its

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a concrete technical design is hard: assumptions go unstated, alternatives go unweighed, and decisions get lost. This Skill structures that process into a guided dialogue that ends with a written design doc. ## Core Features & Use Cases - Context Exploration: Reads existing project plans, findings, and code before asking questions, so it never asks what the codebase can answer. - Clarifying Dialogue: Asks questions one at a time, each with a recommended answer and alternatives, until the problem is crisply stated. - Approach Comparison: Proposes 2-3 implementation approaches with tradeoffs (cost, risk, blast radius, maintenance) plus a single clear recommendation. - Design Doc Output: Writes a dated design doc to docs/brainstorm/ with an Open questions section that feeds the next pipeline stage. - Use Case: You have a vague idea like "add caching to the API layer." Run the brainstorm to explore the codebase, clarify scope, compare caching strategies, and get a design doc ready for stress-testing. ## Quick Start Ask the AI to brainstorm a design for the feature you are about to build, for example by saying "brainstorm how to add rate limiting to our API endpoints."

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn a rough feature idea into a technical design doc?▼

Run the brainstorm with your topic. It explores existing project plans and code first, asks clarifying questions one at a time with recommended answers, proposes 2-3 approaches with tradeoffs, then writes a dated design doc to docs/brainstorm/.

What is the difference between brainstorming and writing an implementation plan?▼

Brainstorming is generative: it explores context and proposes approaches with a recommendation, producing a design doc. Planning (handled by the write-plan step) breaks a settled design into Goals, Micro-Goals, and Tasks. Brainstorm first, plan after decisions are resolved.

Can I use this for product ideation or market validation?▼

No. This is technical design only: how to build something, not whether the market wants it. Product ideation and requirements discovery belong to separate pm-discovery skills, per the stated boundaries.

What happens to unresolved questions after the design doc is written?▼

Unresolved threads go into the Open questions section of the design doc, phrased as decidable questions. That section is the input for the grill-me step, which walks each question one branch at a time and records resolved decisions.

Why does the brainstorm ask questions one at a time instead of all at once?▼

One-at-a-time questioning keeps the dialogue focused and lets each answer shape the next question. Every question leads with a recommended answer and one-line rationale, and anything the codebase can answer is explored instead of asked.