grill-me

Conduct adversarial interviews that walk decision trees one question at a time.

2|Updated Mar 16, 2021
One-click install
npx skills add https://github.com/karitham/dotfiles --skill grill-me-karitham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/karitham/dotfiles/tree/main/modules/opencode/skills/grill-me
Command: npx skills add https://github.com/karitham/dotfiles --skill grill-me-karitham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial interview mode that walks the full decision tree one question at a time. Activated when the user wants more rigor than normal discussion — stress-testing a plan, getting grilled on a design, or mentions "grill me", "help me decide", "what are the options", "tradeoffs", "RFC", "design doc".

Core Features & Use Cases

  • Adversarial review that isolates assumptions and exposes weak points.
  • Structured decision-tree mapping with one question per turn.
  • Use cases include design reviews, architecture decisions, and RFC-style planning.

Quick Start

Ask the system to grill your plan by requesting one concrete question at a time and waiting for your answer before proceeding.

Frequently Asked Questions about grill-me

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an adversarial review to stress-test my RFC or design doc?

An adversarial review stress-tests your RFC by walking the full decision tree one question at a time. This structured cadence isolates assumptions and exposes weak points in your design doc before implementation.

What is a decision-tree interview for architecture decisions?

A decision-tree interview for architecture decisions maps out dependencies and challenges your plan sequentially. It requires a strict one-question cadence, waiting for your answer before proceeding to expose tradeoffs and failure modes.

How do I identify tradeoffs and failure modes in my technical planning?

You identify tradeoffs and failure modes in technical planning by conducting an adversarial interview. This approach isolates assumptions and explicitly documents weak points across your architecture decisions or RFC.

Can I use adversarial review for risk analysis on my design?

Yes, you can use adversarial review for risk analysis on your design. It challenges your plan by mapping the full decision tree, isolating hidden assumptions, and explicitly documenting tradeoffs and potential failure modes.

When do I need an adversarial review instead of a normal design discussion?

You need an adversarial review when you want more rigor than a normal design discussion provides. It is ideal for stress-testing a plan, evaluating an RFC, or mapping tradeoffs when you mention being grilled on a design.

What are the limitations of using a one-question cadence for design reviews?

The limitation of a one-question cadence for design reviews is that it requires clearly defined decision dependencies and strict adherence to waiting for an answer before proceeding, which may slow down rapid brainstorming.