brainstorming

Turn raw ideas into validated design plans and persist them to docs.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Clay-HHK/claude-config --skill brainstorming-clay-hhk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Clay-HHK/claude-config/tree/main/skills/superpowers/brainstorming
Command: npx skills add https://github.com/Clay-HHK/claude-config --skill brainstorming-clay-hhk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that no implementation begins without a validated design by guiding users through context exploration, focused clarification, and structured design presentation to avoid wasted work and hidden assumptions.

Core Features & Use Cases

  • Structured Discovery: Walks through exploring project context, reviewing files and docs, and asking one clarifying question at a time.
  • Option Comparison: Proposes 2–3 approaches with trade-offs and a clear recommendation to inform decisions.
  • Validated Design & Handoff: Presents sectioned designs, obtains user approval, writes a committed design doc in docs/plans/YYYY-MM-DD-<topic>-design.md, and transitions to implementation planning via the writing-plans skill.
  • Use Case: Use before adding a new feature, changing configuration, or building a UI component to capture requirements, weigh alternatives, and prevent rework.

Quick Start

Begin by asking the assistant to help brainstorm and design a feature: ask one clarifying question, propose 2-3 approaches with trade-offs, and present a recommended design for my approval.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn raw feature ideas into implementation-ready design plans?

Feature scoping and design planning prevents wasted work by capturing requirements, weighing alternatives, and validating assumptions before implementation. It ensures no coding begins without an approved design document.

What is the best way to compare design approaches for a new UI component?

Structured ideation compares 2-3 approaches with explicit trade-offs and a recommendation, ensuring you evaluate alternatives against requirements before committing to implementation.

How do I document validated design decisions before writing code?

Write committed design docs to docs/plans/YYYY-MM-DD-<topic>-design.md, persisting approved sectioned design specifications for reference throughout the development project.

Does brainstorming a design specification require existing project files?

Structured discovery reviews existing project files and docs to explore context before asking focused clarifying questions, ensuring proposed designs align with your current codebase.

Can I use this approach for backend component design and configuration changes?

Apply structured design planning to feature scoping, UI and backend component design, small utilities, configuration changes, and pre-implementation planning to prevent hidden assumptions.

What happens after a design plan is approved?

After approval and persistence to a markdown file, the process transitions to implementation planning by invoking the writing-plans skill to guide subsequent development work.