grilling

Interrogates a design plan one-question-at-a-time to surface assumptions and decisions.

16|2|Updated Mar 29, 2018
One-click install
npx skills add https://github.com/khoi/dotfiles --skill grilling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grilling
Source: https://github.com/khoi/dotfiles/tree/main/chezmoi/dot_agents/skills/grilling
Command: npx skills add https://github.com/khoi/dotfiles --skill grilling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Relentlessly interrogate a plan to surface assumptions and decisions.

Core Features & Use Cases

  • One-question-at-a-time grilling: Guides the user through every design branch with focused prompts.
  • Dependency and risk tracing: Identifies dependencies between decisions and surfaces potential risk areas.
  • Use Case: When finalizing a new feature, iteratively challenge every assumption to reach a shared design.

Quick Start

Ask one precise, targeted question at a time about the plan to reach a shared understanding.

Frequently Asked Questions about grilling

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

FAQPage Schema
How do I surface assumptions in a design plan before implementation?

To surface assumptions in an architecture plan, you can use an interrogation flow that asks one targeted question at a time. This method relentlessly challenges your decisions to reach a shared understanding and identify dependencies.

What is the best way to interrogate design requirements during early-stage reviews?

The best way to interrogate design requirements is through a question-by-question grilling process. It preserves context and sequencing while tracing dependencies to validate your strategy and expose hidden risks.

Can I use a one-question-at-a-time flow to validate architecture planning?

Yes, you can use a one-question-at-a-time flow to validate architecture planning. This approach iteratively challenges every design branch and decision to ensure dependency resolution and clear strategy validation.

How do I trace dependencies and risks when finalizing a new feature design?

You trace dependencies and risks by applying an interrogation flow to your feature design. This surfaces potential risk areas and maps dependencies between decisions by guiding you through every branch with focused prompts.

When should I interrogate a plan for decision-making clarity?

You should interrogate a plan for decision-making clarity during early-stage design reviews, architecture planning, or strategy validation. It helps surface assumptions and reach a shared design before finalizing implementation.