grilling

Stress-tests plans and ideas through structured rounds of numbered interview questions.

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill grilling-pikachu0310
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grilling
Source: https://github.com/pikachu0310/codex-agent-ops-public/tree/main/.agents/skills/grilling
Command: npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill grilling-pikachu0310

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and decisions often contain hidden assumptions and unexplored branches that only surface after implementation begins. This Skill interviews the user relentlessly, mapping every decision as a design tree so nothing is silently assumed before action is taken. ## Core Features & Use Cases - Design Tree Mapping: Models a plan as a tree of decisions where each choice branches into dependent sub-decisions. - Frontier-Based Rounds: Asks only the questions whose prerequisites are settled, numbering each question and providing a recommended answer per round. - Fact Delegation: Dispatches sub-agents to look up facts from the filesystem or tools instead of asking the user for information that can be retrieved automatically. - Use Case: Before starting a migration project, invoke the Skill to be grilled on scope, rollback strategy, and dependencies until every decision is explicitly confirmed. ## Quick Start Ask the assistant to grill you on your plan for the upcoming feature launch and answer each numbered round of questions until the frontier is empty.

Frequently Asked Questions about grilling

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

FAQPage Schema
How do I stress-test a plan before implementing it?

Use a structured interview approach that maps your plan as a design tree of decisions. Each round asks only the questions whose prerequisites are settled, with recommended answers, until no assumptions remain unexamined.

What is a design tree in decision planning?

A design tree models every decision as a node that branches into the sub-decisions depending on it. The frontier is the set of questions answerable now, and each answered round pushes the frontier outward to unblock dependent questions.

Can the assistant look up facts instead of asking me?

Yes. When a question needs a fact from the filesystem or tools, a sub-agent is dispatched to find it. Only questions downstream of that fact wait; the rest of the frontier is asked immediately.

When should I not use a grilling-style interview?

Avoid it for trivial or time-critical tasks where the cost of multi-round questioning exceeds the risk of a wrong assumption. It is designed for consequential plans where silent assumptions are expensive.

How does the interview session end?

The session ends when the frontier is empty, meaning every branch of the design tree has been visited. The assistant does not act on the plan until the user confirms a shared understanding has been reached.