grill-me

Interrogate plans through decision-tree traversal to resolve dependencies and reach consensus.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kagenti/humr --skill grill-me-kagenti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/kagenti/humr/tree/main/.agents/skills/grill-me
Command: npx skills add https://github.com/kagenti/humr --skill grill-me-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Relentlessly interrogates a plan to reach a shared understanding, identifying gaps and dependencies across branches of the decision tree.

Core Features & Use Cases

  • Systematically probes assumptions and requirements to surface risks.
  • Walks through each branch of the design decision tree and documents dependencies and conflicts.
  • Applies to design reviews, architecture planning, and strategy sessions where clear alignment is needed.

Quick Start

Ask the AI to grill your plan step by step until all branches are explored and consensus is reached.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I interrogate a design plan to reach shared understanding across branching decisions?

To interrogate a design plan for shared understanding, you systematically probe assumptions and requirements within a conversational flow. This resolves branching decisions by traversing the decision tree to surface risks, gaps, and dependencies.

What is the best way to identify dependencies and conflicts across a decision tree?

Identifying dependencies across a decision tree requires walking through each branch to document conflicts and assumptions. Applying interactive questioning during design reviews or architecture planning ensures all branching paths are explored and resolved.

How do I conduct an interactive requirements analysis for architecture planning?

Interactive requirements analysis for architecture planning involves relentlessly questioning the proposed strategy step by step. This conversational probing exposes hidden risks and ensures team alignment before finalizing roadmap decisions.

Can I use conversational probing for roadmap planning and strategy sessions?

Yes, conversational probing applies directly to roadmap planning and strategy sessions. It systematically questions the plan to ensure dependencies are resolved and shared consensus is reached across all explored decision branches.

When do I need to resolve branching decisions in a design review?

You need to resolve branching decisions in a design review when multiple architectural paths exist and clear alignment is required. Traversing the decision tree interactively surfaces gaps and conflicts before finalizing the plan.

Why does my team lack shared understanding during architecture discussions?

Your team lacks shared understanding during architecture discussions because hidden assumptions and unresolved dependencies remain across decision branches. Systematically interrogating the plan step by step exposes these gaps and forces consensus.