メニュー
Interview the user or a design relentlessly until reaching shared understanding. Walk down every branch of the decision tree, resolving dependencies one by one. Use when stress-testing a plan, clarifying design, or the user says "grill me".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Find deepening opportunities in the codebase — refactors that reduce coupling, simplify interfaces, and improve AI-navigability. Use when improving architecture, finding refactoring opportunities, or making a codebase easier to work with.
Use before any feature work — explores intent, asks clarifying questions one at a time, produces a design doc. Invoke before writing any code or plan.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "less tokens", or invokes /caveman.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → review. Use when something is broken, throwing errors, or regressing.
Use at the start of any session to understand which skill to invoke. Maps the full workflow — feature development, bug fixing, architecture, and utilities — for a C++ game server project with SVN.
Compact the current conversation into a handoff document for another agent or session to pick up.
| name | grill |
| description | Interview the user or a design relentlessly until reaching shared understanding. Walk down every branch of the decision tree, resolving dependencies one by one. Use when stress-testing a plan, clarifying design, or the user says "grill me". |
Interview relentlessly about every aspect of a plan or design until reaching shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one by one.
For each question, provide your recommended answer so the user can agree, correct, or redirect.
When grilling a game server design, specifically probe:
setChanged()? When is it saved to DB?ErrorDefine.sdp?ADD_NORMAL_COMMAND in CmdRegister.h?User: "I want to add a daily reward system"
Grill: "Should the daily reward reset at midnight server time or at a rolling 24h window
from the player's last claim? I'd recommend midnight server time — it's simpler to reason
about and consistent with most other daily systems in the codebase."
User: "Midnight server time"
Grill: "Should claiming the daily reward be possible while the player is offline (e.g. via
an automated system) or only when they actively log in? I'd recommend login-only — it keeps
the flow simple and doesn't require a background job."
... and so on