菜单
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 职业分类
Use this skill whenever a task would benefit from authoritative, technology-specific input beyond generalist knowledge — for example during code review, implementation planning, or troubleshooting, whenever the code, design, or issue touches Rust, Bun runtime TypeScript/JavaScript, Java/Spring Cloud microservices, GIS/geospatial processing, web front-end code, or Datadog observability data. This skill identifies the relevant expert sub-agent(s) for the technology or domain in scope, delegates to them via the Task tool, and synthesizes their findings into a single, actionable answer for the calling skill or user.
Use the ax CLI instead of curl + throwaway parsing scripts whenever you fetch a URL, explore an unknown web page, or extract structured data from HTML. Trigger whenever you are about to write an inline script (python3 heredoc, node -e, regex over HTML) or a bare curl for one-off web fetching, scraping, or page exploration.
This skill analyzes a given improvement ticket or idea and provides a detailed plan on how to implement it. It gathers relevant information from the ticket or request, including context, requirements, and constraints, and generates a step-by-step implementation plan. The skill also identifies potential challenges, required tests, and validation steps, and can assist in creating prototypes or breaking down the implementation into smaller tasks or milestones. When the implementation touches a technology with a dedicated expert (e.g. Rust, Bun/TypeScript, Java/Spring Cloud, GIS, web front-end, or Datadog observability), it consults the `ask-the-expert` skill to validate the proposed approach, risks, and tradeoffs before finalizing the plan.
Use this skill when the user wants recently written or modified code reviewed, needs targeted feedback on code quality, security, performance, idiomatic usage, or architecture, or has specific technical questions about their codebase. This skill delegates to the `ask-the-expert` skill to identify the languages and technologies involved and consult the appropriate specialized experts, then synthesizes their findings into a single, prioritized review.
This skill analyzes a given problem or issue and provides a detailed troubleshooting plan to resolve it. It gathers relevant information from the problem description, including context, symptoms, and constraints, and generates a step-by-step troubleshooting plan. The skill also identifies potential causes, required tests, and validation steps, and can assist in creating prototypes or breaking down the troubleshooting into smaller tasks or milestones. When the issue touches a technology with a dedicated expert (e.g. Rust, Bun/TypeScript, Java/Spring Cloud, GIS, web front-end, or Datadog observability), it consults the `ask-the-expert` skill for root-cause input before finalizing the plan.
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
| 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. |
| metadata | {"github-path":"skills/productivity/grilling","github-ref":"refs/tags/v1.1.0","github-repo":"https://github.com/mattpocock/skills","github-tree-sha":"0ace40ac10f5c0b1534324e4e109ebfa831fb361"} |
| name | grilling |
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.
