grill-me

Interrogate design decisions with question-by-question prompts and dependency tracking.

160|16|Updated Dec 4, 2024
One-click install
npx skills add https://github.com/MaggieAppleton/maggieappleton.com-V3 --skill grill-me-maggieappleton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/MaggieAppleton/maggieappleton.com-V3/tree/main/.claude/skills/planning-and-product/grill-me
Command: npx skills add https://github.com/MaggieAppleton/maggieappleton.com-V3 --skill grill-me-maggieappleton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interviewing and challenging a plan or design to reach a shared understanding, surface assumptions, and reveal dependencies by walking through every design branch.

Core Features & Use Cases

  • Relentless questioning: guides the user through every decision point to surface risks and dependencies.
  • Branch-aware analysis: tracks decision trees and surfaces conflicting requirements with recommended resolutions.
  • Codebase-aware exploration: when possible, explores the codebase to ground questions in implementation details.

Quick Start

Grill me step-by-step on my plan until we reach a shared understanding, exploring each branch and providing recommended answers.

Frequently Asked Questions about grill-me

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

FAQPage Schema
What is a design review interrogation and how does it surface hidden dependencies?

A design review interrogation challenges every decision point to surface assumptions and reveal dependencies by walking through each branch. It ensures shared understanding of product plans when requirements are uncertain or conflicting.

How do I grill a product plan step by step to reach a shared understanding?

To grill a product plan, apply strict question-by-question prompts that track decision trees and surface conflicting requirements. This step-by-step interrogation explores each branch and recommends concrete paths to resolve uncertainties.

Can I use a decision tree analysis to resolve conflicting requirements during product planning?

Yes, branch-aware decision tree analysis tracks every design decision to surface conflicting requirements. It guides stakeholders through each point to provide recommended resolutions and ensure a shared understanding of the plan.

Does this questioning approach work for codebase exploration and implementation reviews?

Yes, this questioning approach works for codebase exploration by grounding questions in implementation details. It interrogates codebase decisions to ensure shared understanding and recommends concrete paths when exploring the structure.

What's the best way to prepare stakeholders for a rigorous design review session?

The best way to prepare stakeholders is to frame the session as a relentless questioning process that walks through every decision branch. This surfaces risks, assumptions, and dependencies before committing to the product plan.

When should I avoid using a relentless questioning method for requirement gathering?

You should avoid using relentless questioning when requirements are already crystal clear and stakeholders share a complete understanding. It is designed for uncertain or conflicting plans where hidden dependencies and assumptions need surfacing.