grill-me

Interrogate plan elements through branch-aware interactive questioning with documented decisions.

2|1|Updated Oct 8, 2009
One-click install
npx skills add https://github.com/riethmayer/dotfiles --skill grill-me-riethmayer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/riethmayer/dotfiles/tree/main/stow/agents/.agents/skills/grill-me
Command: npx skills add https://github.com/riethmayer/dotfiles --skill grill-me-riethmayer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Relentlessly interview stakeholders to surface assumptions, map decisions, and align on a shared plan, reducing miscommunication and rework.

Core Features & Use Cases

  • Structured, branching questioning to exhaustively explore design choices and dependencies.
  • Guides design reviews and planning sessions, capturing decisions and rationale for future reference.
  • Supports iterative deep dives when exploring complex plans, ensuring no branch remains unresolved.

Quick Start

Begin the interview by outlining the goal and then ask a focused question to reveal assumptions and dependencies.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I interrogate stakeholders to surface assumptions during design reviews?

Interrogate stakeholders through structured, branching interviews that surface assumptions and dependencies to reach shared understanding, reducing miscommunication and rework.

What is the best way to map decision trees and dependencies during planning sessions?

Map decision trees using a branch-aware interactive interview workflow that guides planning sessions with clear prompts and fallback paths to exhaustively explore design choices and document decisions.

How do I document decisions and rationale from strategy workshops?

Document decisions by guiding strategy workshop participants through iterative deep dives and relentless questioning that captures choices and dependencies, ensuring no branch remains unresolved.

Can I use this interview approach for complex plans with unresolved branches?

Yes, you can use this interview approach for complex plans because it supports iterative deep dives with fallback paths, ensuring every plan element is exhaustively questioned until shared understanding is reached.

When do I need a branch-aware questioning workflow for design choices?

You need a branch-aware questioning workflow when design choices have complex dependencies requiring exhaustive exploration, providing clear prompts and fallback paths to ensure no branch remains unresolved.