brainstorm

Category: Data & AI | Uploader: havingautism | Downloads: 0 | Version: v1.0（Latest）

Lightweight brainstorming skill. Use when a feature or behavior request has multiple reasonable approaches and the missing piece is user preference, tradeoff choice, or key constraint.

Changelog: Source: GitHub https://github.com/havingautism/Codemini-CLI

Directory Structure

Current level: tree/main/skills/brainstorm/

📄 SKILL.md 2.4 KB

SKILL.md

---
name: brainstorm
description: Lightweight brainstorming skill. Use when a feature or behavior request has multiple reasonable approaches and the missing piece is user preference, tradeoff choice, or key constraint.
version: 0.2.0
---

Use this skill only when the task needs clarification or option comparison before coding.

**Announce:** When entering brainstorm, say "Using brainstorm to explore approaches before implementation."

## Anti-Pattern

Do NOT skip this skill for tasks that appear straightforward but lack clear requirements or constraints. Underspecified tasks cause the most wasted work. Even a few seconds of clarification beats a wrong implementation.

## Process

1. **Ask one question at a time.** If a key uncertainty remains, ask the next best question and STOP. Wait for the user's answer.
2. **Give 2-3 short options** only when the blocking constraint is already clear. Keep options concrete and focused on the main tradeoff.
3. **Present conclusions as suggested decisions**, not final choices.
4. **Do NOT write code, pseudo-code, file edits, or broad repo exploration** while direction is still being chosen.

## Output Formats

### Mode A: key constraint missing

```
Question:
- ask: <one specific question>
- why this matters: <1-2 sentences on what this decides>
```

Wait for the user's answer. Do NOT proceed with options or code.

### Mode B: goal is clear but approach choice remains

```
Option 1:
- idea: <concrete approach>
- pros: <1-2 points>
- cons: <1-2 points>

Option 2:
- idea: <concrete approach>
- pros: <1-2 points>
- cons: <1-2 points>

Option 3 (optional):
- idea: <concrete approach>
- pros: <1-2 points>
- cons: <1-2 points>

Suggested decision:
- recommended: <option N>
- reason: <why>
```

## Self-Review

Before presenting options or a suggested decision, quickly check:

- Are all options actually different, or are two of them the same idea in different words?
- Does the recommended option match the user's stated constraints?
- Did I invent requirements the user never mentioned? Remove them.

## Exit

After the user approves a direction:

- If the task is small and clear enough to implement directly → proceed to code.
- If the task is non-trivial or touches multiple areas → YOU MUST invoke `writing-plans` to create an implementation plan before coding.

Do NOT stop at the brainstorm conclusion when the natural next step is planning.

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

brainstorm

Directory Structure

SKILL.md

Report

Notice