菜单
对一个已有的 plan 或 design 做对抗式压测：沿决策树逐个分支追问，直到与用户达成共同理解。 一次只问一个问题，每个问题都给出你的推荐答案；能从 codebase 查到的就去查，不要问用户。 触发词："grill me"、"拷问我"、"压测这个计划"、"挑战我的设计"、"stress-test the plan"， 或用户希望在动手前把计划/设计的每个决策点逼到清晰。 不用于开放式头脑风暴、方向选型，或已经明确、无歧义的任务。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Manual-first brainstorming workflow for turning ambiguous ideas or competing directions into an approved decision before planning or implementation. Activate when the user explicitly asks to brainstorm, explore options, compare approaches, or pressure-test a direction. Do not activate for clarification, review, detailed planning, or straightforward execution once a direction is already chosen.
Hybrid workflow for turning ambiguous implementation requests into actionable scope before execution. Use explicitly when the user asks to clarify requirements, disambiguate a request, or spec a change before building it. Activate automatically only when an implementation-oriented request contains direct contradictions, missing acceptance criteria that would materially change the build, or an explicit request to proceed with documented assumptions. Do not activate for open-ended direction-finding, brainstorming, or already-specific actionable tasks.
Audit a repository's control-plane health and produce an actionable improvement report. Use when the user asks to "audit the repo", "check repo health", "assess control plane", "entropy audit for the control system", "check what's missing for agents", or wants to know what's missing in their instruction files, rules, and verification infrastructure. Do NOT use for code review (use review), dependency audit (use dependency-audit), general documentation work (use project-documentation), or reviewing a specific PR or diff (use review or entropy-review).
Review code changes for entropy introduction: naming drift, error-model splits, dependency violations, doc staleness, and pattern duplication. Activate when the user asks for "entropy review", "consistency check", "drift check on this PR", "check if this change introduces new patterns", or wants a review focused on naming, error handling, or structural consistency rather than correctness. Do NOT activate for general code review (use review), full repo audit (use repo-entropy-audit), control-plane audit (use control-plane-auditor), brainstorming, or implementation tasks.
Manual-first architecture methodology for system design and technology selection using problem-first framing, stack-agnostic trade-offs, uncertainty handling, and future-aware decision lenses. Use when a project needs architecture direction or selection decisions; do not use for pure implementation planning, narrow stack research, or review-only tasks.
Create GitHub issues from PRD or requirements. Auto-detects complexity - simple tasks create single issue, complex tasks create epic + sub-issues structure. Uses gh cli with unified labels.
| name | grill-me |
| description | 对一个已有的 plan 或 design 做对抗式压测：沿决策树逐个分支追问，直到与用户达成共同理解。 一次只问一个问题，每个问题都给出你的推荐答案；能从 codebase 查到的就去查，不要问用户。 触发词："grill me"、"拷问我"、"压测这个计划"、"挑战我的设计"、"stress-test the plan"， 或用户希望在动手前把计划/设计的每个决策点逼到清晰。 不用于开放式头脑风暴、方向选型，或已经明确、无歧义的任务。 |
| invocation_posture | hybrid |
| version | 0.1.0 |
在动手之前，把一个 plan/design 的每个决策点逐一逼到清晰。这是对抗式压测，不是温和澄清：你扮演挑刺者，沿决策树深挖，直到未言明的假设、隐藏依赖和模糊边界全部暴露并解决。
Invocation posture: hybrid。优先显式调用；自动触发仅限明确的"压测计划/设计"意图，不用于一般想法探索。
brainstorming / future-aware-architectureclarify（grill-me 针对已有计划做对抗，不做从零需求澄清）grill-with-docs 的职责；本 skill 只对话、不写任何文档orders.ts:88 支持部分取消——以哪个为准？"）。stage-change-pipeline Stage 2）的输入。grill-with-docs 的职责，本 skill 刻意不做）。clarify：从零把模糊需求变 actionable scope。grill-me 假设计划已存在，专做对抗式压测。可串联：clarify 产出 scope → grill-me 压测该 scope/design。stage-change-pipeline：在 Stage 1 收尾、创建 OpenSpec change（Stage 2）之前，用 grill-me 压测阶段计划与设计文档，把假设和边界逼清，降低 Stage 3 审核返工。brainstorming / future-aware-architecture：负责"做什么 / 选哪条路"；grill-me 负责"这条路的每个决策是否真的想清楚了"。改编自 mattpocock/skills 的 grill-me（中文参考 vinvcn/mattpocock-skills-zh-CN），按本仓库 skill 规范本地化，并接入 stage-change-pipeline 工作体系。原作的文档持久化变体见 grill-with-docs（本 skill 刻意不含其 CONTEXT.md/ADR 写入行为）。