brainstorming

Explores ambiguous project ideas and writes actionable design specifications.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/51hhh/BU03 --skill brainstorming-51hhh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/51hhh/BU03/tree/main/.github/skills/brainstorming
Command: npx skills add https://github.com/51hhh/BU03 --skill brainstorming-51hhh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps turn vague ideas into clear, reviewable designs and specifications before any implementation work begins. It reduces wasted effort by uncovering requirements, constraints, and success criteria early.

Core Features & Use Cases

  • Context exploration: Reviews the current project state, docs, and recent changes before proposing a direction.
  • Clarifying dialogue: Asks one question at a time to refine purpose, scope, and constraints.
  • Approach comparison: Presents 2-3 options with trade-offs and a recommendation before settling on a design.
  • Spec creation and review: Writes a design doc, checks it for gaps or contradictions, and prepares it for user approval.
  • Use case: Planning a new feature, changing behavior in an existing app, or decomposing a larger initiative into smaller implementation-ready pieces.

Quick Start

Use the brainstorming skill to help me clarify the goal, scope, constraints, and success criteria for this idea before we decide on any implementation.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn ambiguous ideas into approved design specifications?

Turning ambiguous ideas into approved design specifications involves context discovery, one-question-at-a-time clarification, and proposing alternative approaches with trade-offs before drafting a self-reviewed design doc for approval.

What is the best way to define project scope and constraints before implementation?

Defining project scope and constraints before implementation requires a clarifying dialogue that uncovers requirements, success criteria, and constraints early, reducing wasted effort by settling on an approved design direction first.

Can I use this to plan changes to existing app behavior?

Yes, you can use this to plan changes to existing app behavior. It supports early-stage planning for behavior changes in existing applications by reviewing the current project state and recent changes before proposing a design direction.

Does this brainstorming approach work for decomposing large initiatives into smaller pieces?

Yes, this brainstorming approach works for decomposing large initiatives. It supports multi-subsystem initiatives by breaking them down into smaller, implementation-ready pieces with clear specifications and success criteria.

What are the limitations of using a spec creation workflow for product planning?

A limitation of this spec creation workflow is that it requires user interaction at approval gates, meaning it cannot autonomously finalize designs without human review and explicit approval of the generated design doc.