菜单
Collaborative discovery and design framing for ambiguous or high-risk work. Use when requirements are unclear, multiple approaches are possible, or you need to turn an idea into a validated design brief before planning or coding.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Execute an approved implementation plan exactly and safely. Use for ExecPlan-style plan execution, resumable phase checklists, multi-hour implementation work, migrations, significant refactors, and plans that require verification checkpoints, status tracking, and final reporting.
Create detailed, execution-ready implementation plans for complex or high-risk changes without coding. Use for ExecPlan-style work, multi-hour changes, significant refactors, migrations, resumable phase checklists, and work that should be handed off to execute-plan with clear validation.
Create source-adjacent HTML visualizations for /visualize requests, docs, markdown, standardized plans, process flows, charts, Mermaid diagrams, context maps, and recommendation diagrams.
Structured clarification and requirements gathering through focused dialogue or with dry code. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed.
Create or refresh project documentation in `docs/`. Use when a project needs docs initialized or existing docs synced to the current codebase.
Diagnose and fix bugs with root-cause analysis and verification. Use when you have a concrete issue report, failing behavior, runtime error, or test regression that should be resolved safely. Stop and escalate to brainstorm when scope or risk grows.
| name | brainstorm |
| description | Collaborative discovery and design framing for ambiguous or high-risk work. Use when requirements are unclear, multiple approaches are possible, or you need to turn an idea into a validated design brief before planning or coding. |
| argument-hint | [brief description of the idea or problem to solve] |
| license | MIT |
Use this skill to convert rough ideas into clear, reviewable design outputs through structured dialogue.
The goal is to:
Load only the project context relevant to the current idea:
docs/SUMMARY.md exists, read it first.Code Standard docs for implementation conventions.Also check key implementation files relevant to the idea and note constraints from existing architecture, dependencies, and conventions.
Keep this pass focused. Only gather what is needed for the current idea.
Ask targeted questions sequentially to remove ambiguity with interactive input/question tool:
Do not jump to implementation details too early.
Propose 2-5 viable approaches.
For each approach, include:
Lead with your recommended option and explain why it best fits the project context and constraints.
After presenting all approaches, use interactive input/question tool to let the user pick their preferred approach. List the summary options. Example:
with the tag added for the recommended approach to guide the user.
After user selection, present the design incrementally with sections:
After presenting, use input/question tool immediately to ask whether to:
After you and the user have worked through requirements and the design is validated, determine the next actions.
Use input/question tool to present the user with three high-level next actions:
write-plan handoff with visualization.Only perform this step after the user has explicitly chosen "Write artifacts" during Step 5.
Persist results to the standardized location:
docs/.brainstorms/YYMMDD-HHmm-<topic-slug>/docs/.brainstorms/YYMMDD-HHmm-<topic-slug>/SUMMARY.mddocs/.brainstorms/YYMMDD-HHmm-<topic-slug>/section-01-<slug>.mddocs/.brainstorms/YYMMDD-HHmm-<topic-slug>/section-02-<slug>.mdSUMMARY.md format: strictly follow the template inside references/summary-template.md.
Once the draft artifacts exist, use input/question tool again to validate them with options: