grill-master

Interviews users with focused questions to clarify requirements before planning or implementation.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/BING0116-gif/math-AI-assistant --skill grill-master-bing0116-gif
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-master
Source: https://github.com/BING0116-gif/math-AI-assistant/tree/main/.agents/skills/grill-master
Command: npx skills add https://github.com/BING0116-gif/math-AI-assistant --skill grill-master-bing0116-gif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams and individuals often jump into planning or coding with vague requirements, leading to rework, misaligned designs, and missed edge cases. This Skill enforces a structured Socratic interview that surfaces assumptions, constraints, and unknowns before any plan or code is produced. ## Core Features & Use Cases - Structured Requirement Interrogation: Walks every branch of the design tree—goals, data models, interfaces, UX flows, constraints, and risks—one focused question at a time. - Codebase-Informed Clarification: Inspects the repository to answer questions from facts instead of asking the user to recall implementation details. - Shared-Understanding Checkpoint: Produces a confirmed summary of goals, decisions, open questions, and risks before handing off to planning or implementation skills. - Use Case: Before adding a weekly summary email feature to a SaaS app, use this Skill to clarify metrics, delivery pipelines, and failure modes, then hand the confirmed requirements to a spec-writing or coding skill. ## Quick Start Ask the assistant to grill you on your next feature idea or study topic before writing any plan or code.

Frequently Asked Questions about grill-master

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

FAQPage Schema
How do I clarify requirements before writing a plan or code?▼

Invoke the grill-master skill and answer its focused questions one at a time. It restates your goal, explores each design branch, and only produces a confirmed summary of requirements before suggesting a planning or implementation skill.

What is a Socratic interview approach for software design?▼

It is a structured questioning method that walks every branch of the design tree—goals, data models, interfaces, constraints, and risks—asking one focused question at a time. The goal is a shared, testable understanding before any plan or code exists.

Does the skill inspect my codebase during the interview?▼

Yes. When an answer depends on existing behavior, APIs, or data structures, the skill inspects the repository and summarizes what the code actually does, then asks its next question based on those facts rather than guesses.

When should I not use an interrogation-style requirements skill?▼

Skip it when requirements are already fully specified and confirmed, or for trivial one-line changes. The skill is designed for ambiguous topics, new features, and designs where assumptions and edge cases remain unresolved.

What happens after the requirements interview is complete?▼

The skill summarizes goals, key decisions, constraints, open questions, and risks, then asks you to confirm or correct the summary. Only after explicit confirmation does it recommend handing off to a planning skill such as a spec writer or a coding skill.