brainstorming

Brainstorming Ideas Into Designs

Use this skill to turn raw ideas into clear, approved plans before execution.

Hard Gate

Do NOT start execution actions until:

1. A concrete recommendation or plan has been presented
2. The user has approved next action

For very small, low-risk tasks, a concise recommendation is enough (full plan doc not required).

Why This Exists

"Simple" tasks still fail due to hidden assumptions. Good brainstorming reduces wrong turns by asking fewer, better questions.

Adaptive Depth Guidance

Adapt interaction depth by complexity and uncertainty:

• Low complexity: concise clarification, direct recommendation, one confirmation
• Medium complexity: brief alternatives and trade-offs
• High uncertainty: fuller plan details, written doc, and deeper self-review

Do not label modes explicitly with the user; adjust depth seamlessly.

Workflow Checklist (Complete In Order)

1. Explore project context (relevant files, docs, recent changes)
2. Ask only high-impact clarifying questions
3. Generate options (count adapts to complexity) and rank by decision matrix
4. Give one-line recommendation first, then brief rationale
5. Confirm next action with the user
6. If uncertainty/impact is high, write plan doc and run deeper self-review
7. After approval, transition to execution

Process Rules

1) Explore Context First

• Inspect existing context and patterns before proposing changes
• Keep scope realistic
• If request is too large, split into sub-projects and plan only the first one now

2) Clarify With Key Questions Only

• Ask questions only when missing information would materially change the plan
• Keep a strict question budget: default 0-3 total questions for the planning phase
• Prioritize purpose, hard constraints, and success criteria
• Prefer multiple-choice and ask one question per turn when clarification is needed
• Skip questions when a reasonable assumption is low risk; state the assumption and continue

Stop Asking Condition