Menu
Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.
Use when CrossFrame Suite routes explicit Chinese casebook work: turning materials into reusable cases, anonymized entries, mechanisms, and retrieval indexes.
Use only when the user explicitly names crossframe-critical for a Chinese structural critique dossier, article plan, or long-form critical essay.
Use when CrossFrame Suite routes explicit Chinese proposition testing, debate analysis, hidden-premise review, rebuttal design, or withdrawal condition checks.
Use when CrossFrame Suite routes explicit Chinese reader replies, editor responses, consultation-style short answers, or boundary-aware structural advice.
Use when explicit CrossFrame work needs a Chinese critical insight essay, commentary, concept essay, public piece, or structure-to-article draft after diagnosis.
Use when CrossFrame Suite routes explicit Chinese notes for books, theories, articles, excerpts, bidirectional reading, absorption, or conflict mapping.
| name | brainstorming |
| description | Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration. |
| risk | unknown |
| source | community |
| date_added | 2026-02-27 |
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.
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.
Before asking any questions:
Do not design yet.
Your goal here is shared clarity, not speed.
Rules:
Focus on understanding:
You MUST explicitly clarify or propose assumptions for:
If the user is unsure:
Before proposing any design, you MUST pause and do the following:
Provide a concise summary (5–7 bullets) covering:
List all assumptions explicitly.
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.
Once understanding is confirmed:
This is still not final design.
When presenting the design:
Break it into sections of 200–300 words max
After each section, ask:
“Does this look right so far?”
Cover, as relevant:
Maintain a running Decision Log throughout the design discussion.
For each decision:
This log should be preserved for documentation.
Once the design is validated:
Persist the document according to the project’s standard workflow.
Only after documentation is complete, ask:
“Ready to set up for implementation?”
If yes:
You may exit brainstorming mode only when all of the following are true:
If any criterion is unmet:
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.
This skill is applicable to execute the workflow or actions described in the overview.
