home / skills / hxk622 / tokendance / brainstorming
This skill helps turn vague ideas into structured designs and specs through guided, one-question-at-a-time brainstorming sessions.
npx playbooks add skill hxk622/tokendance --skill brainstormingReview the files below or copy the command above to add this skill to your agents.
---
name: brainstorming
display_name: 头脑风暴
version: 1.0.0
author: system
description: "创意工作前的必备技能 - 用于探索用户意图、需求和设计。适用于创建功能、构建组件、添加新特性或修改行为。You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior."
tags: [brainstorm, ideation, design, creative, thinking, planning, 头脑风暴, 创意, 设计, 思考, 规划, feature, requirements, 需求分析]
allowed_tools: []
max_iterations: 20
timeout: 300
enabled: true
match_threshold: 0.65
priority: 8
---
# Brainstorming Ideas Into Designs
## Overview
Help turn ideas into fully formed designs and specs through natural 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.
## The Process
**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`
- Use elements-of-style:writing-clearly-and-concisely skill if available
- Commit the design document to git
**Implementation (if continuing):**
- Ask: "Ready to set up for implementation?"
- Use superpowers:using-git-worktrees to create isolated workspace
- Use superpowers:writing-plans to create detailed implementation plan
## Key Principles
- **One question at a time** - Don't overwhelm with multiple questions
- **Multiple choice preferred** - Easier to answer than open-ended when possible
- **YAGNI ruthlessly** - Remove unnecessary features from all designs
- **Explore alternatives** - Always propose 2-3 approaches before settling
- **Incremental validation** - Present design in sections, validate each
- **Be flexible** - Go back and clarify when something doesn't make sense
This skill guides collaborative idea exploration and turns raw concepts into validated designs and specs before any creative or coding work begins. It enforces a disciplined, incremental process: learn the project context, ask focused questions one at a time, propose alternatives, and present the design in small, verifiable sections. Use this as the mandatory first step whenever you plan features, components, or behavior changes.
Start by inspecting the current project context: files, docs, and recent work. Ask a single, preferably multiple-choice question to clarify intent or constraints. Iterate through focused questions until the purpose, constraints, and success criteria are clear, then propose 2–3 approaches with trade-offs and a recommended path. Present the chosen design in 200–300 word sections, pausing after each to confirm alignment before continuing.
How many questions should I expect before a full design?
There is no fixed number; continue one-question-at-a-time until purpose, constraints, and success criteria are clear—often 3–8 focused questions.
Why present designs in small sections?
Small sections make validation fast and reduce rework by confirming alignment continuously instead of after a large deliverable is complete.