grill-me

Guide iterative one-question-at-a-time design reviews to reveal decisions and dependencies.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/mappa-ai/skills --skill grill-me-mappa-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/mappa-ai/skills/tree/main/utils-skills/grill-me
Command: npx skills add https://github.com/mappa-ai/skills --skill grill-me-mappa-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interview teams to uncover hidden assumptions and dependencies by guiding a structured, exhaustive questioning process that resolves each branch of a plan.

Core Features & Use Cases

  • One-question-at-a-time interview loop
  • Branch-aware exploration of design decisions
  • Codebase-grounded questioning when possible
  • Documentation of decisions and dependencies for traceability

Quick Start

Ask one question at a time about the plan and dependencies to reach a shared understanding.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I guide a structured design review to uncover hidden dependencies?

Uncover hidden dependencies by guiding an iterative, one-question-at-a-time design review. This structured interview loop exhaustively questions each branch of a plan to resolve assumptions and document decisions for team traceability.

What is a one-question-at-a-time approach for architecture planning?

A one-question-at-a-time approach for architecture planning enforces a strict interview cycle that explores branching decisions sequentially. It grounds questions in your codebase when possible, revealing dependencies and recording decisions for traceability.

Can I use this iterative questioning method for product strategy sessions?

Yes, you can apply this iterative questioning method to product strategy sessions. It guides branch-aware exploration of product design decisions, documenting each choice and dependency to ensure comprehensive strategy alignment and traceability.

How do I document decisions and dependencies during product design discussions?

Document decisions and dependencies during product design discussions by running an exhaustive, branch-aware questioning process. It records each resolved design choice and its associated dependencies automatically as the interview loop progresses.

Does this design review tool explore the codebase to ground its questions?

Yes, the design review tool explores the codebase when possible to ground its questions. This ensures the iterative, one-question-at-a-time interview loop accurately reflects your actual architecture and dependencies during planning.