grill-me

Interrogate plans and designs through structured branch-by-branch questioning.

Updated May 4, 2024

Search Tags:#planning #decision tree #interview #design review #codebase exploration #risk analysis

Ready to run

npx skills add https://github.com/kcrlee/dots --skill grill-me-kcrlee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/kcrlee/dots/tree/main/claude/.claude/skills/grill-me
Command: npx skills add https://github.com/kcrlee/dots --skill grill-me-kcrlee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you expose weak assumptions, hidden dependencies, and unresolved choices in a plan or design before you commit to it.

Core Features & Use Cases

Structured Challenge: Asks targeted follow-up questions to clarify goals, constraints, tradeoffs, and failure modes.
Branch-by-Branch Resolution: Walks through each decision path until the remaining options are understood and documented.
Codebase-Aware Reasoning: If an answer can be verified from the repository, it checks the codebase instead of guessing.
Use Case: Use it when you want a design review, a pre-mortem, or a rigorous sanity check on a proposed approach.

Quick Start

Ask me to grill your plan or design until every major assumption, dependency, and decision branch is resolved.

Frequently Asked Questions about grill-me

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

FAQPage Schema

How do I pressure-test a technical design to expose hidden dependencies and weak assumptions?▼

Pressure-test a technical design by applying structured branch-by-branch questioning to clarify goals, constraints, and failure modes until shared understanding is reached and no ambiguity remains.

What is a structured design review for ambiguous workflows and when do I need it?▼

A structured design review interrogates ambiguous workflows through targeted follow-up questions to document unresolved choices and tradeoffs. You need it before committing to a proposed approach to prevent failure.

How do I conduct a pre-mortem risk analysis on a proposed product decision?▼

Conduct a pre-mortem risk analysis by walking through each decision path of a product decision to challenge goals, trace dependencies, and document potential failure modes before implementation begins.

Can I verify design review answers directly against my codebase during exploration?▼

You can verify answers directly against your codebase. The review process checks repository contents to trace dependencies and validate assumptions instead of guessing when answers can be found in the code.

What is the best way to resolve ambiguous decision trees in a software engineering plan?▼

The best way to resolve ambiguous decision trees is through branch-by-branch interrogation, asking targeted questions to clarify each option and document the remaining tradeoffs until all paths are understood.

Are there limitations to using structured questioning for codebase exploration and dependency tracing?▼

Limitations apply when answers cannot be verified from repository contents. If codebase exploration cannot trace the dependencies or validate the assumptions, the questioning process cannot resolve the ambiguity.