grill-me

Clarifies vague requirements into verifiable requirement checklists through layered questioning.

5|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/A158Coke/WotbTools --skill grill-me-a158coke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/A158Coke/WotbTools/tree/main/.agents/skills/grill-me
Command: npx skills add https://github.com/A158Coke/WotbTools --skill grill-me-a158coke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague one-line requests and ambiguous requirement drafts lead to misaligned implementations and wasted development effort. This Skill turns fuzzy asks into a written, verifiable requirement confirmation sheet before any planning or coding begins. ## Core Features & Use Cases - Layered Questioning: Asks at most 3 prioritized questions per round across semantic, value, constraint, and risk layers, each with a proposed default answer the user can simply confirm or correct. - Requirement Confirmation Sheet: Produces a written document covering goal, scope, non-goals, acceptance criteria, key assumptions, and open items (split into blocking vs. defaultable), written into docs/current-plan.md. - Workflow Handoff: After confirmation, hands off to a plan-designer step for implementation planning, keeping requirement clarification strictly separate from coding. - Use Case: A user says "help me build a replay feature" without specifics. The Skill restates its understanding, asks targeted questions about what "replay" means and how success is measured, then outputs an acceptance-ready requirement sheet. ## Quick Start Tell the assistant: "I want to add a damage leaderboard feature but I'm not sure about the details—grill me on the requirements first."

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I turn a vague feature idea into clear requirements?

Restate your understanding of the goal first, then ask layered questions covering semantics, value, constraints, and risks. Limit each round to three questions with proposed default answers so the requester only confirms or corrects rather than answering from scratch.

What should a requirement confirmation document include?

A requirement confirmation sheet should include a one-sentence goal, scope and non-goals, measurable acceptance criteria, key assumptions, and open items split into blocking versus defaultable. Writing it down prevents verbal-only agreements from drifting during implementation.

When should requirement clarification happen in a development workflow?

Requirement clarification should happen before any planning or coding, whenever a request is a single sentence, contains ambiguous terms, or the requester is unsure what they want. It complements post-implementation review by catching scope problems early.

How many questions should I ask when clarifying requirements?

Ask at most three questions per round, ordered by importance, and only block on questions that affect scope or fundamental approach. Non-blocking uncertainties should proceed with stated default assumptions rather than waiting for answers.

What are the limitations of a requirement clarification skill?

A requirement clarification skill only defines boundaries and acceptance criteria; it does not evaluate whether a requirement is good, design the implementation, or write code. Those steps belong to downstream planning and development stages.