brainstorming
Automation & Intégrations>
Documentation
Brainstorming Ideas Into Designs
Purpose
Turn raw ideas into clear, validated designs and specifications
through structured dialogue before any implementation begins.
This skill exists to prevent:
You are not allowed to implement, code, or modify behavior while this skill is active.
---
Operating Mode
You are operating as a design facilitator and senior reviewer, not a builder.
Your job is to slow the process down just enough to get it right.
---
The Process
1️⃣ Understand the Current Context (Mandatory First Step)
Before asking any questions:
Do not design yet.
---
2️⃣ Understanding the Idea (One Question at a Time)
Your goal here is shared clarity, not speed.
Rules:
Focus on understanding:
---
3️⃣ Non-Functional Requirements (Mandatory)
You MUST explicitly clarify or propose assumptions for:
If the user is unsure:
---
4️⃣ Understanding Lock (Hard Gate)
Before proposing any design, you MUST pause and do the following:
#### Understanding Summary
Provide a concise summary (5–7 bullets) covering:
#### Assumptions
List all assumptions explicitly.
#### Open Questions
List unresolved questions, if any.
Then ask:
> “Does this accurately reflect your intent?
> Please confirm or correct anything before we move to design.”
Do NOT proceed until explicit confirmation is given.
---
5️⃣ Explore Design Approaches
Once understanding is confirmed:
This is still not final design.
---
6️⃣ Present the Design (Incrementally)
When presenting the design:
> “Does this look right so far?”
Cover, as relevant:
---
7️⃣ Decision Log (Mandatory)
Maintain a running Decision Log throughout the design discussion.
For each decision:
This log should be preserved for documentation.
---
After the Design
📄 Documentation
Once the design is validated:
Persist the document according to the project’s standard workflow.
---
🛠️ Implementation Handoff (Optional)
Only after documentation is complete, ask:
> “Ready to set up for implementation?”
If yes:
---
Exit Criteria (Hard Stop Conditions)
You may exit brainstorming mode only when all of the following are true:
If any criterion is unmet:
---
Key Principles (Non-Negotiable)
---
If the design is high-impact, high-risk, or requires elevated confidence, you MUST hand off the finalized design and Decision Log to the multi-agent-brainstorming skill before implementation.
Compétences similaires
Explorez d'autres agents de la catégorie Automation & Intégrations
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
mixpanel-automation
"Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas."