{
  "id": "grill-me",
  "handle": "grill-me",
  "canonicalUrl": "https://bestskillsforclaude.com/en/skills/grill-me",
  "language": "en",
  "alternates": {
    "en": "https://bestskillsforclaude.com/en/skills/grill-me",
    "es": "https://bestskillsforclaude.com/es/skills/grill-me",
    "pt-BR": "https://bestskillsforclaude.com/pt-br/skills/grill-me",
    "ja": "https://bestskillsforclaude.com/ja/skills/grill-me"
  },
  "category": {
    "id": "engineering-discipline",
    "name": "Engineering discipline"
  },
  "publisher": {
    "name": "Matt Pocock",
    "url": "https://github.com/mattpocock"
  },
  "source": "https://github.com/mattpocock/skills",
  "documentation": null,
  "licenseAsStated": "MIT",
  "runtime": "Claude Code and agents that support the skills CLI",
  "lastReviewed": "2026-08-05",
  "headline": "What if the agent asked you the hard questions instead?",
  "summary": "The plan you cannot defend out loud is the plan that will fail in week three.",
  "verdict": "The grill-me skill reverses the usual direction: instead of answering your questions, it interrogates you about a plan or design until every unresolved branch is either decided or explicitly deferred. It is the fastest way to find the decision you have been quietly avoiding.",
  "bestFor": "Design decisions, architecture choices and specifications before implementation starts.",
  "skipIf": "The work is mechanical and there is nothing to decide.",
  "keyTakeaways": [
    "Being questioned surfaces gaps faster than being advised.",
    "Answers you invent under pressure are the ones to double check afterwards.",
    "It pairs with brainstorming and writing-plans, which sit on either side of it.",
    "It cannot supply domain knowledge you do not have. It only finds where it is missing."
  ],
  "quickStart": [
    "Install it with the skills CLI from mattpocock/skills, published under MIT.",
    "Bring a real plan, not a topic. It interrogates decisions, not intentions.",
    "Write down every answer you had to invent on the spot. Those are the actual gaps."
  ],
  "sections": [
    {
      "heading": "What it changes in practice",
      "paragraphs": [
        "Most plans fail on the parts nobody wanted to discuss: migration, error paths, who owns the data, what happens to existing customers. Those are exactly the parts a friendly review skips.",
        "An interrogation surfaces them because it keeps pulling on branches rather than approving the shape. The discomfort is the mechanism, not a side effect."
      ]
    },
    {
      "heading": "Where it disappoints",
      "paragraphs": [
        "It can grind. Not every branch deserves resolution before implementation, and deferring some deliberately is a legitimate answer that you have to give explicitly.",
        "It also cannot check facts about your organisation. It will accept a confident answer that happens to be wrong."
      ]
    }
  ],
  "faq": [
    {
      "question": "How is this different from asking for a review?",
      "answer": "A review evaluates what you wrote. This questions you until the undecided parts of the plan are visible."
    },
    {
      "question": "When should I use it?",
      "answer": "Before implementation, on anything where a wrong decision is expensive to reverse."
    },
    {
      "question": "Does it need a written plan?",
      "answer": "Yes, bring a real plan. A topic produces vague questions and vague answers."
    }
  ],
  "sources": [
    {
      "label": "mattpocock/skills on GitHub",
      "url": "https://github.com/mattpocock/skills",
      "kind": "repository"
    },
    {
      "label": "Agent skills directory listing",
      "url": "https://skills.sh",
      "kind": "directory"
    }
  ],
  "machineReadable": {
    "markdown": "https://bestskillsforclaude.com/en/skills/grill-me/content.md",
    "json": "https://bestskillsforclaude.com/en/skills/grill-me/skill.json"
  },
  "disclosure": "Editorial desk review based on the publisher's own repository. Not a security audit, a benchmark or a guarantee of maintenance."
}