菜单
Interrogate a plan or design relentlessly — walk each branch of the decision tree and resolve every open decision until nothing vague remains. Use to stress-test a plan, surface edge cases and gaps you missed, get grilled on a design, or when you mention "grill me".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Analyze unresolved PR review comments and recommend whether to fix, skip, or optionally address each. Use when a PR has review comments and you need a verdict on how to respond.
Create a git commit. Use when ready to commit changes. Creates conventional commit messages focused on why, not what.
Open a pull request for the current branch. Use when code is ready for review. Creates concise descriptions focused on the problem being solved.
Karpman Drama Triangle analysis for communication and conflict. Use when reviewing emails, proposals, or scripts for hidden drama dynamics, coaching difficult conversations, analyzing interpersonal conflict, or reframing victim/hero/villain patterns into Creator/Challenger/Coach alternatives.
Audit codebase, assess technical debt, analyze architecture, find structural problems. Use when evaluating code health, planning refactors, or need architectural review. Covers brittleness, coupling, complexity.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
| name | grill-me |
| description | Interrogate a plan or design relentlessly — walk each branch of the decision tree and resolve every open decision until nothing vague remains. Use to stress-test a plan, surface edge cases and gaps you missed, get grilled on a design, or when you mention "grill me". |
| argument-hint | Plan file or description |
| model | opus |
Interrogate me relentlessly about a plan or design until we share the same mental model. Walk each branch of the decision tree, resolving dependencies one at a time, until nothing underspecified remains.
If given a plan file ($ARGUMENTS), read it first and identify which categories below apply. Then start grilling.
| Category | Example question |
|---|---|
| Scope boundaries | "What explicitly is NOT included?" |
| Failure modes | "What happens when X fails? How does the user recover?" |
| Data edge cases | "What if the input is empty? Huge? Malformed?" |
| State transitions | "Can a user be in states A and B at once? Then what?" |
| Performance limits | "At what scale does this break down?" |
| Migration | "How do existing users and their data transition?" |
| Alternatives | "Why this over X? What would make X the better choice?" |
| Dependencies | "What external services does this rely on? Fallback if they're down?" |
Done when every applicable category is resolved: no "it depends" left, edge cases and failure modes are concrete, and dependencies between decisions are settled.
If grilling a plan file, offer to fold the resolved decisions back into it — scope (in and out), technical approach, edge cases and error handling, and any open questions that remain.
