brainstorming

Plans and executes structured brainstorming sessions to convert ideas into designs and specifications.

5|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/jsloat/superpowers-for-copilot --skill brainstorming-jsloat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/jsloat/superpowers-for-copilot/tree/main/skills/brainstorming
Command: npx skills add https://github.com/jsloat/superpowers-for-copilot --skill brainstorming-jsloat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming Ideas Into Designs helps teams turn vague ideas into concrete designs and specs through structured, collaborative dialogue. Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.

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; 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; Be ready to go back and clarify if something doesn't make sense
  • 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 using-git-worktrees skill to create isolated workspace; Use writing-plans skill to create detailed implementation plan

Quick Start

Describe the current idea and generate a modular design outline in 200-300 word sections, asking one clarifying question at a time

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn vague product ideas into concrete designs and specifications?

Structured brainstorming converts vague ideas into concrete designs by analyzing project context, asking targeted clarification questions, evaluating approaches, and delivering modular design documents with iterative validation.

What is the best way to evaluate different architecture approaches during early-stage product development?

Evaluating architecture approaches during product development is best handled by proposing 2-3 options conversationally, leading with a recommended choice, and explaining the trade-offs and reasoning before finalizing the design.

How do I structure a design review to ensure all components and data flows are covered?

Structure a design review by presenting the design in 200-300 word sections, asking after each section if it looks right, and systematically covering architecture, components, data flow, error handling, and testing.

Can I use structured ideation for feature planning without writing code immediately?

Structured ideation supports feature planning without immediate coding by validating designs iteratively, writing the finalized spec to a markdown design document, and committing it directly to git for later implementation.

How do I refine project requirements when the initial idea is unclear?

Refine unclear project requirements by asking questions one at a time, preferring multiple choice when possible, and focusing on understanding the purpose, constraints, and success criteria before exploring architectural approaches.