grill-me

Guide structured design interviews to explore design trees and log decisions.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/johwer/marketplace --skill grill-me-johwer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/johwer/marketplace/tree/main/skills/grill-me
Command: npx skills add https://github.com/johwer/marketplace --skill grill-me-johwer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forces thorough design conversation before premature planning or implementation. Based on Frederick P. Brooks' "design tree" concept: walk down each branch, resolve dependencies between decisions one by one.

Core Features & Use Cases

  • Phase 1 — Frame the problem: Identify the user pain point, audience, success criteria, and blockers.
  • Phase 2 — Walk the design tree: For each major decision, explore both branches and establish upstream/downstream dependencies (data model, API, UI, permissions, migration, etc.).
  • Phase 3 — Challenge assumptions: Probe hidden assumptions with targeted questions and explore alternative approaches.
  • Phase 4 — Confirm shared understanding: Summarize decisions, open questions, risks, and next steps; decide if ready to proceed to ticketing.
  • Style: Be relentless but constructive — the goal is clarity, not gotchas
  • After the Interview: Provide a draft decision log, ticket ideas, and an alignment plan.

Quick Start

Start a guided design exploration interview by framing the problem and walking the design tree through all major branches before proposing any solution.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I explore a design tree before writing code or tickets?

Exploring a design tree before coding involves guiding a structured interview to frame the problem, walk down each decision branch, and resolve dependencies across data models, APIs, and UI to produce a documented decision log.

What is a structured product design interview for feature ideation?

A structured product design interview is a staged conversation that identifies user pain points and success criteria, challenges hidden assumptions, and confirms shared understanding before architecture choices are finalized.

How do I document design decisions and create an alignment plan?

Documenting design decisions requires summarizing the explored design branches, open questions, and risks from the interview into a draft decision log with ticket ideas and an alignment plan for next steps.

Can I use a structured design exploration for architecture choices and migrations?

Yes, structured design exploration supports architecture choices by mapping upstream and downstream dependencies including data models, API structures, permissions, and migration paths across multiple design branches.

When should I challenge assumptions during product design discussions?

You should challenge assumptions during product design discussions after walking the design tree, probing hidden assumptions with targeted questions to explore alternative approaches before confirming shared understanding.

What are the limitations of skipping design exploration before ticketing?

Skipping design exploration before ticketing risks premature planning by failing to resolve dependencies between decisions, leading to misaligned architecture choices and undocumented risks during implementation.