菜单
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
A relentless interview to sharpen a plan or design.
Reviews text for weasel words, vague language, and corporate jargon using Amazon's writing principles. Returns flagged issues and a polished version. Use when drafting Slack updates, PR descriptions, Jira tickets, or any professional communication that needs to be direct and concrete.
Captures high-value learnings from a skill execution and applies targeted improvements to the SKILL.md. Generic: works for any skill. Invoke right after running a skill when steps diverged from the documented flow, new techniques were discovered, or undocumented edge cases appeared. Synthesizes from conversation context automatically.
Audits and rewrites CLAUDE.md files. Use when the user asks to review, optimize, rewrite, standardize, or improve a CLAUDE.md file. Triggers include "audit claude.md", "otimiza o claude.md", "melhora o claude.md", "padroniza claude.md", "review CLAUDE.md". Also use when someone says "clean up my docs", "my claude context is messy", or asks to "initialize" context files in a project.
Pre-close session review. Scans for loose ends before ending a conversation — documentation gaps, unsaved memory, open checklist items, uncommitted git changes, and notification gaps. Reports findings grouped by category; never acts without confirmation. Invoke at the end of any work session before signing off.
| name | grilling |
| description | Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases. |
| author | Matt Pocock |
| upstream | https://github.com/mattpocock/skills · skills/productivity/grilling/SKILL.md |
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. For each question, provide your recommended answer.
Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.
If a fact can be found by exploring the codebase, look it up rather than asking me. The decisions, though, are mine — put each one to me and wait for my answer.
Do not enact the plan until I confirm we have reached a shared understanding.
