菜单
Invoke this skill anytime you are creating a plan—such as crafting an RFC, writing a PRD, starting a new app, or proposing an architecture change. It will relentlessly interview the user to resolve all dependencies and edge cases.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Continue an in-progress /grill-me session in auto-pilot — the agent keeps asking the same relentless questions, but answers each one with its own best recommendation and moves on. The user no longer types answers; they interrupt (Esc) only when they disagree. Use to power through long grilling sessions once you and the agent are clearly aligned.
Hand a goal-maker board off to Codex (gpt-5.5, low reasoning by default) — Claude validates the board, runs `codex exec` with the /goal directive, captures the output, re-validates, and reports state changes. Use after /goal-maker bootstraps the charter and state.yaml when you want Codex (cheaper at low reasoning, separate context) to actually execute the PM loop while Claude Code stays the orchestrator. Triggers on "codex-goal", "run goal in codex", "delegate goal to codex", "hand to codex", or "/goal" when the user is in Claude Code (which doesn't have /goal natively).
Cross-agent code review: run OpenAI Codex to review your changes, then address its feedback. Use when asked to "codex review", "get a second opinion", "cross-review", "have codex review this", or "external review". Works with uncommitted changes, specific commits, or branch diffs.
Set up a rolling Scout/Judge/Worker task board with a charter, machine-truth state.yaml, and durable receipts for long-running autonomous coding work. Use when a goal is broad, multi-hour, ambiguous, recovery-flavored, or needs serial discipline (one active task at a time) instead of parallel teammates. Triggers on "goal-maker", "set up a goal", "create a charter", "rolling task board", "scout/judge/worker", "PM-owned board", or when the user wants long-running autonomous work that's NOT a parallel swarm and NOT a multi-milestone mission. Pairs with /grill-me upfront and /principles
Measure and lower CRAP (Change Risk Anti-Patterns) — a metric that fuses cyclomatic complexity and test coverage to surface fragile code. Use when verifying test quality after a feature, gating PRs, refactoring legacy code, setting up a new project's quality bar, or whenever the user mentions "CRAP score", "complexity", "Change Risk Anti-Patterns", or wants to know which functions are most likely to break. Pair with mutation-testing so coverage is meaningful, not superficial.
Bootstrap CLAUDE.md as a short table-of-contents plus a structured docs/ directory (agent guidance, architecture, product specs, acceptance tests, ADRs, exec plans, quality grades). Use when CLAUDE.md is missing, when asked to "create CLAUDE.md", "bootstrap project", or "set up agent context".
| name | grill-me |
| description | Invoke this skill anytime you are creating a plan—such as crafting an RFC, writing a PRD, starting a new app, or proposing an architecture change. It will relentlessly interview the user to resolve all dependencies and edge cases. |
Use this skill anytime a plan is being created. Examples include:
Principle #6 (Find what's hard — that's the value) and Principle #4 (Document intent and surface assumptions) — grill-me is the operational tool for both. The interview's job is to surface the genuinely hard sub-problem (so disproportionate effort lands there) AND to make tacit assumptions explicit before they become silent bugs. End every grilling with: "What did we assume that we didn't write down?" See /principles.
When this skill is invoked, adopt the following directive:
Interview the user 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.
