菜单
Split a complex problem into focused sub-sessions. Use when a brainstorm has too many independent dimensions to address in a single session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Stress-test phase for brainstorming. System 2 evaluation with full judgment - stress-test decisions, simplify ruthlessly, polish until elegant. Use after decide phase has selected a clear path.
Divergent thinking phase for brainstorming. System 1 exploration with zero judgment - generate options, explore directions, build on keywords. Use when exploring a new problem space after grounding.
Generate retrievable artifacts from brainstorm sessions. Use after STRESS phase to create ADR + Spec + Plan (technical) or Outline (conceptual). Spawns parallel architect subagents to generate inline mermaid diagrams.
Brainstorm session using the Arete cognitive protocol
Convergent thinking phase for brainstorming. System 2 analytical evaluation - synthesize options into decision matrix, force prioritization, challenge choices. Use after explore phase when ready to narrow down options.
Problem discovery phase. Investigative mode - understand the real problem before solving.
| name | decompose |
| description | Split a complex problem into focused sub-sessions. Use when a brainstorm has too many independent dimensions to address in a single session. |
Break a multi-faceted problem into focused brainstorm sessions that can each go through the full GROUND → SHIP flow independently.
List the distinct sub-problems. Each should be independently brainstormable:
Sub-sessions identified:
1. [Problem A] — [core tension in 1 sentence]
2. [Problem B] — [core tension in 1 sentence]
3. [Problem C] — [core tension in 1 sentence]
Which sub-problems depend on decisions from others?
Dependencies:
- Problem B depends on Problem A (schema choice affects migration)
- Problem C is independent
Recommended order:
1. Problem A (others depend on it)
2. Problem C (independent — can run in parallel)
3. Problem B (blocked by A)
Ask the user which sub-problem to tackle first. Continue the current session on that one only. Other sub-problems are parked — not forgotten, just deferred.
In later sessions, reference prior session outputs from context/exports/ for decisions that carry forward. This is how sub-sessions compose into a coherent whole.
Concise. Present the decomposition as a structured list, not a wall of text. Let the user react and choose.
Don't decompose problems that are genuinely coupled. If changing one dimension necessarily changes the others, it's one problem — not three. Ask: "Can I decide A without knowing B?" If not, they stay together.