Grill me

Skill tyecode/skills/skills/productivity/grill-me

Personal AI agent skills for better coding. Fixes common agent failure modes: misaligned requirements, blind coding, debugging loops, and lost context between sessions.

Install

npx -y skills add tyecode/skills --skill grill-me

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Interviews the user about a plan until requirements are fully resolved and shared understanding is reached. Use when user mentions "grill me", requirements are vague, or before starting something significant.

SKILL.md

1.8 KB, as published. Nobody here has run it

Skill: grill-me

When to Use This Skill

Use this skill when:

User says "grill me" before starting work
Requirements are vague and need sharpening
You're about to build something significant and want to reduce risk of building the wrong thing

The Process

Ask one question at a time. Do not ask multiple questions in one message.

For each question:

State your recommended answer with a short reason
Ask the user to confirm, correct, or choose differently

Before asking a question that can be answered by reading the codebase, read the codebase first. Don't ask what you can discover yourself.

What to Cover

Walk the decision tree until every branch is resolved:

Goal — What does success look like? How will you know it's done?
Scope — What's in? What's explicitly out?
Users — Who uses this? What do they need?
Data — What data is created, read, updated, deleted?
Edge cases — What happens when inputs are invalid, missing, or extreme?
Errors — How should failures be handled and surfaced?
Integration — What existing systems does this touch?
Constraints — Any deadline, performance, or compatibility requirements?

Stop when you can write a one-paragraph spec that the user confirms is correct.

When to Stop

Stop asking when you have enough to write a spec. Over-grilling is as harmful as under-grilling — at some point you're just delaying work.

If the user says "just start" before you're done, note the open questions explicitly and proceed with your best assumptions stated.