brainstorming

Guide structured dialogue to turn vague ideas into design documents.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/kgadek/kgadek-claude-plugin --skill brainstorming-kgadek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/kgadek/kgadek-claude-plugin/tree/main/ai-spec/2026-01-21-sdd-inspirations/references/obra-superpowers/skills/brainstorming
Command: npx skills add https://github.com/kgadek/kgadek-claude-plugin --skill brainstorming-kgadek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help turn ideas into fully formed designs and specs through natural collaborative dialogue.

Core Features & Use Cases

  • Understanding the idea: Check out the current project state first (files, docs, recent commits), ask questions one at a time to refine the idea, prefer multiple choice questions when possible, but open-ended is fine too, and only one question per message; if a topic needs more exploration, break it into multiple questions; focus on understanding: purpose, constraints, success criteria.
  • Exploring approaches: Propose 2-3 different approaches with trade-offs; Present options conversationally with your recommendation and reasoning; Lead with your recommended option and explain why.
  • Presenting the design: Once you believe you understand what you're building, present the design; Break it into sections of 200-300 words; Ask after each section whether it looks right so far; Cover: architecture, components, data flow, error handling, testing.
  • After the Design: Documentation: Write the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md; Commit the design document to git.
  • Implementation (if continuing): Ask: "Ready to set up for implementation?" Use superpowers: using-git-worktrees to create isolated workspace; Use superpowers: writing-plans to create detailed implementation plan.
  • Key Principles: One question at a time; Multiple choice preferred; YAGNI ruthlessly; Explore alternatives; Incremental validation; Be flexible.

Quick Start

Begin by understanding the current project context, then proceed with the guided, one-question-at-a-time design exploration.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn a vague product idea into a concrete design specification?

Guided brainstorming converts vague ideas into concrete designs and specifications through a structured, multi-step dialogue that captures decisions, rationale, and next steps. It checks current project context, then asks incremental questions to refine constraints and success criteria.

What is the best way to explore design approaches and document the final decision?

The best way to explore design approaches is proposing 2-3 options with trade-offs conversationally, leading with a recommendation and reasoning. After validation, the final design decision is documented to a markdown file and committed to git.

Can I use a conversational format to refine requirements for early-stage product features?

Yes, you can use conversational dialogue to refine requirements for early-stage product features. The process asks one multiple-choice or open-ended question per message to clarify purpose, constraints, and success criteria without overwhelming you.

How do I structure a design presentation to avoid overwhelming stakeholders?

To avoid overwhelming stakeholders, structure a design presentation by breaking it into sections of 200-300 words. Present architecture, components, data flow, error handling, and testing incrementally, asking after each section whether it looks right.

What to do after finalizing a design spec to prepare for implementation?

After finalizing a design spec, you prepare for implementation by creating an isolated git workspace and writing a detailed implementation plan. This ensures the validated design document transitions smoothly into actionable coding steps.