brainstorming

Original：🇨🇳 Chinese

Translated

You must use it before any creative work - creating features, building components, adding functionality, or modifying behavior. Explore user intentions, requirements, and design before implementation.

1installs

Sourcezhucl1006/ailesuperpowers

Added on2026-02-25

NPX Install

npx skill4agent add zhucl1006/ailesuperpowers brainstorming

SKILL.md Content (Chinese)

View Translation Comparison →

Translating Brainstormed Ideas into Design

Overview

Help transform ideas into complete designs and specifications through natural collaborative dialogue.

First understand the current project background, then ask one question at a time to refine the idea. Once you understand what you're building, break the design into small sections (200-300 words) and check if it looks correct so far after each section.

Process

Understanding the Idea:

First check the current project status (documents, files, recent commits)
Ask one question at a time to refine the idea
Choose multiple-choice questions whenever possible, but open-ended questions are also acceptable
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 trade-off approaches
Present options along with your recommendations and reasoning through dialogue
Start with your recommended option and explain why

Presenting the Design:

Once you're confident you understand what you're building, present the design
Break it into sections of 200-300 words
Ask if it looks correct so far after each section
Cover: architecture, components, data flow, error handling, testing
Be prepared to go back and clarify if something doesn't make sense

Post-Design

Documentation:

Write the validated design into
```
docs/plans/YYYY-MM-DD-<topic>-design.md
```
Use stylistic elements if possible: clear and concise writing techniques
Commit the design document to git

Implementation (if proceeding):

Ask: "Ready to implement?"
Use superpower: using-git-worktrees to create isolated workspaces
Use superpower: writing plans to develop a detailed implementation plan

Key Principles

One Question at a Time - Don't overwhelm with multiple questions
Prefer Multiple Choice - Easier to answer than open-ended when possible
Relentless YAGNI - Remove unnecessary features from all designs
Explore Alternatives - Always propose 2-3 approaches before settling
Incremental Validation - Present the design in sections and validate each part
Stay Flexible - Go back and clarify when something doesn't make sense