Skip to content

Instantly share code, notes, and snippets.

@Turbo87
Created July 23, 2026 09:08
Show Gist options
  • Select an option

  • Save Turbo87/9e729a8fcf329860c04e3404eaa7dff4 to your computer and use it in GitHub Desktop.

Select an option

Save Turbo87/9e729a8fcf329860c04e3404eaa7dff4 to your computer and use it in GitHub Desktop.
Brainstorm Skill
interface:
display_name: "Brainstorm"
short_description: "Shape rough ideas into designs"
default_prompt: "Use $brainstorm to turn a rough idea into a design and spec."
name brainstorm
description Guide structured brainstorming from a rough idea into a design, specification, and eventual implementation plan. Use when the user wants to brainstorm, talk through an idea, refine a product or technical design, turn an idea into a spec, or asks for one-question-at-a-time ideation. Do not implement during the brainstorm unless the user explicitly exits brainstorming.

Brainstorm

Help the user turn an initial idea into a coherent design and spec through focused questions and staged synthesis.

Workflow

  1. Build enough project context to understand the starting point.
  2. Inspect relevant files and recent git history when available.
  3. If git history is unavailable, say so and continue with the available file context.
  4. Ask focused questions to refine the idea.
  5. Stop after each question and wait for the user's answer.
  6. When the design direction is clear, synthesize the proposed design before writing an implementation plan.

Questioning

  • Ask one question at a time.
  • Prefer multiple-choice questions when practical.
  • Use open-ended questions when multiple-choice options would hide an important unknown.
  • Do not implement, edit files, or write a plan until the design direction is understood.

Synthesis

When the design is clear enough, stop asking questions and describe the proposed design.

  • Present the design in sections of roughly 200-300 words.
  • After each section, ask whether it looks right so far.
  • Wait for confirmation or correction before continuing to the next section.
  • Cover the eventual implementation plan only after the design and spec have been reviewed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment