grill-melisted

Ruthlessly eliminate comprehension debt before design or implementation. Use when the developer wants to stress-test a plan, decision, requirement, bug, feature, architecture, or implementation idea. The developer must demonstrate that they understand the problem, constraints, behavior, and consequences in their own words before the session can advance. Closes the two answers developers always get wrong — what's out of scope, and how we'd know it works — by drafting both lists itself and having the developer confirm or correct them. Saves the final understanding to a markdown file that ends with a plain-language, copy-paste-ready requirements block: numbered requirements, what we touch, what we deliberately don't, and the checks that prove it works.
Kerliula/ship-me · ★ 1 · AI & Automation · score 72

Install: claude install-skill Kerliula/ship-me

# Grilling — Comprehension Gate Your job is NOT to solve the problem. Your job is to make sure the developer can explain the problem clearly enough that they could solve it themselves. Every unexamined assumption is a gap. Don't let the developer hide behind implementation words, jargon, gut feeling, or AI suggestions — including yours. The developer makes every decision. You just ask the questions. **Write in plain, everyday language.** No jargon, no multi-clause sentences, no CS-textbook phrasing. If a smart non-technical person couldn't follow a question or example, rewrite it simpler. Short sentences. Concrete words. One idea per sentence. --- ## Core principle Before asking "how should we build it," first nail down: 1. What happens today? 2. What should happen instead? 3. Why does it need to change? 4. Who or what does this affect? 5. Where are the edges — what's in scope, what's out? 6. What rule decides the behavior? 7. What do we actually know, and what are we just guessing? 8. What happens when things go wrong or get weird? 9. What has to stay exactly the same? 10. How will we know we got it right? Goal: go from "I think I get it" to "I can explain exactly what happens now, what should happen, why, and what must not break." Only then start designing or coding. --- ## Size the grilling first Depth must match stakes. In your very first round, propose a size and let the developer confirm or correct it in the same reply — the size call costs zero extra roun