菜单
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get roasted on their design, or mentions "brainstorm".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Render a document, a diagram, or a report as HTML for human visualisation.
Use when writing prose meant to read by humans: PR descriptions, docs, blog drafts, emails, design memos
Guidelines on creating issues on GitHub
Run a premortem on any plan, launch, product, hire, strategy, or decision. Assumes it already failed 6 months from now and works backward to find every reason why. Produces a revised plan with blind spots exposed. MANDATORY TRIGGERS: 'premortem this', 'premortem my', 'run a premortem', 'what could kill this', 'future-proof this', 'stress test this plan', 'what am i missing here', 'find the blind spots'. STRONG TRIGGERS: 'what could go wrong', 'am i missing anything', 'poke holes in this', 'where will this break', 'devil's advocate this'. Do NOT trigger on simple feedback requests, or factual questions. DO trigger when someone has a plan or commitment where the cost of being wrong is high.
Schedule a prompt to fire back at yourself at a future time or on a recurring cron pattern. Use when the user says "remind me", "every N minutes/hours/days", "at HH:MM tomorrow", "check X periodically", or otherwise asks for any time-based action. Triggered by the `schedule` tool plus the `/schedule` command for listing and deletion.
Pick one open task and implement it end-to-end as a unit of work. Use when the user asks to pick a task.
| name | brainstorm |
| description | Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get roasted on their design, or mentions "brainstorm". |
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one. Iterate over branches one at a time.
If a question can be answered by exploring the codebase, explore the codebase instead.
NEVER use the AskUserQuestion tool, ask me the questions as part of your text output. For each question, provide your recommended answer.
HARD RULE: ONE question per turn. Then STOP. Wait for reply. No lists. No "and also". No follow-ups. No bundled sub-questions. One ? per response. Violating this defeats the skill.
Index the questions using Q1/Q2/Q3 etc, and index the answers using A/B/C etc. If a decision leads to more nested branches, move those to a new question, don't nest question numbers.
