brainstorming

Guide one-question-at-a-time brainstorming to produce sectioned design outputs.

1|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/gmliao/swift-state-tree --skill brainstorming-gmliao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/gmliao/swift-state-tree/tree/main/.agent/skills/Superpowers/brainstorming
Command: npx skills add https://github.com/gmliao/swift-state-tree --skill brainstorming-gmliao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming is essential to translate vague ideas into concrete design directions. This Skill provides a guided, one-question-at-a-time approach to clarify goals, constraints, and success criteria before implementation, reducing rework and misalignment.

Core Features & Use Cases

  • Structured Ideation: Start from the project context, define goals, and map out requirements.
  • Approach Exploration: Propose 2-3 design approaches with trade-offs to compare options.
  • Incremental Design Delivery: Present the design in small sections (200-300 words each) and validate progressively.
  • Documentation & Handoff: Generate a follow-on design document for handoff to implementation, with next steps and risk notes.

Quick Start

Start brainstorming by clarifying the project goals, context, and constraints. Ask one targeted question at a time to refine the idea, then present a 200-300 word design section and pause for confirmation before continuing.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn raw product ideas into clear design directions?

To turn raw product ideas into clear design directions, use a structured brainstorming process that clarifies goals, constraints, and success criteria through one-question-at-a-time refinement before implementation.

What is the best way to structure ideation for early-stage feature proposals?

The best way to structure ideation for feature proposals is to explore 2-3 design approaches with trade-offs, then validate progressively in small 200-300 word sections before finalizing the direction.

How do I document brainstorming sessions for design handoff?

Document brainstorming sessions for design handoff by generating a follow-on design document that captures the validated design sections, next steps, and risk notes for implementation.

Can I refine requirements by asking one question at a time during design exploration?

Yes, you can refine requirements by asking one targeted question at a time during design exploration to progressively clarify project context, map constraints, and reduce rework.

Why should I present design sections in 200-300 word increments?

Presenting design sections in 200-300 word increments enforces incremental design delivery, allowing you to pause for confirmation and validate each part before continuing to the next.