Brainstorming — Strukturierte Ideation
name: brainstorming
by arn0ld87 · published 2026-04-01
$ claw add gh:arn0ld87/arn0ld87-brainstorming-pro---
name: brainstorming
description: "Facilitates structured ideation sessions for features, products, content, and strategy. Use when: (1) planning new features, (2) exploring product directions, (3) content strategy sessions, (4) creative problem-solving, (5) any scenario requiring divergent thinking before convergence."
---
# Brainstorming — Strukturierte Ideation
> [!CAUTION]
> Beginne **nie** direkt mit Ideen. Starte immer mit Zielklärung:
> 1. Was ist das Problem/die Chance?
> 2. Wer sind die Stakeholder?
> 3. Was sind die Constraints?
> Erst dann: Divergente Phase starten.
---
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.
---
Kernaufgaben
---
Zusammenarbeit mit anderen Skills
| Skill | Verwendung |
|---|---|
| `skill-creator` | Wenn Brainstorming-Ergebnis in Skill umgesetzt wird |
| `product-owner` | Für User-Story-Formulierung nach Ideation |
| `strategy` | Für Roadmap-Integration und OKR-Alignment |
---
Arbeitsablauf (4 Phasen)
Phase 1: Ziel klären
**Assets:**
**Checkliste:**
Phase 2: Divergente Phase
**Assets:**
**Technik-Auswahl:**
| Team-Größe | Zeit | Technik |
|------------|------|---------|
| 1 Person | <30 Min | Mind Mapping |
| 2-6 Personen | 30-40 Min | 6-3-5 oder Brainwriting Pool |
| 6+ Personen | 30-60 Min | SCAMPER oder Role Storming |
Phase 3: Konvergente Phase
**Assets:**
**Prioritäts-Frameworks:**
| Stakeholder | Framework |
|-------------|-----------|
| Demokratisch | Dot-Voting |
| Executive | Value vs. Complexity |
| Data-Driven | RICE-Scoring |
| Customer | Kano-Modell |
Phase 4: Output & Follow-through
**Assets:**
---
Startverhalten
> [!CAUTION]
> Beginne **nie** direkt mit Ideen. Starte immer mit Zielklärung.
**Typischer Start:**
1. "Bevor wir brainstormen: Was ist das Ziel?"
2. "Wer sind die Stakeholder?"
3. "Was sind die Constraints (Budget, Zeit, Compliance)?"
4. "Was ist Erfolg? Wie messen wir das?"
5. Dann: Divergente Phase starten---
Facilitation Scripts
**Assets:**
**Remote-Tools:**
| Kategorie | Tool | Use |
|-----------|------|-----|
| Whiteboard | Miro, Mural, FigJam | Visuelles Brainstorming |
| Video | Zoom, Teams, Meet | Haupt-Session |
| Brainwriting | Mentimeter, Stormboard | Anonyme Ideen |
| Voting | Strawpoll, Tricircle | Schnelle Entscheidungen |
---
Stilregeln
---
Qualitätsmaßstab
Die Ergebnisse sollen wirken, als wären sie erstellt von jemandem, der:
---
References
**Deep-Dives:**
**Decision-Tree:**
Siehe [`framework-matrix.md`](assets/framework-matrix.md) für Technik-Auswahl nach Kontext.
---
The Process
**Understanding the idea:**
**Exploring approaches:**
**Presenting the design:**
After the Design
**Documentation:**
**Implementation (if continuing):**
---
Key Principles
More tools from the same signal band
Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).
Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.
The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...