Have the AI grill you on decisions before it builds, and plans for a fintech app and a vacation rental site changed course

The first question was whether to store uploaded card statements on the server, or analyze them and throw them away. Because the app handles personal financial data, the AI said that “어디까지 저장하고 어디까지 외부(Claude API)로 보내느냐” (how much to store, and how much to send outside to the Claude API) would shape every other decision, and it recommended discarding the originals and keeping only the aggregated results. Each question came with a recommended answer, which he described as “결정 피로를 제거” (removing decision fatigue). youtube

He set it beside the design he had written by hand earlier and judged that the grill-me plan was “비전 내러티브가 더 풍부하지만 구현 디테일은 비어 있다” (richer in vision narrative, but empty on implementation detail). His verdict: it's good for producing a product requirements document (PRD), but turning that into an actual design takes a different skill. youtube

Before adding scroll effects to the website of a private-house rental in Seoul, Sage added one sentence to the end of the request they had been using. The first round brought six questions, and Sage wrote that they were “전부 제가 안 정하고 있던 것들” (all things I hadn't been deciding). The terms were hard to follow, so Sage asked for the questions again in plain words, and five came back. Once the answers were in, the plan had changed like this. gpters

As the reason for the change, Sage wrote “첫 화면은 이미 괜찮았고, 예약 결정은 하우스 페이지에서 일어나기 때문” (the first screen was already fine, and booking decisions happen on the house pages). The answers left one principle: “절제한다. 화면을 붙잡아두지 않는다.” (Hold back. Don't pin the screen in place.) Sage wrote, “/grill-me 한 줄이 그 결정권을 저에게 돌려줬습니다” (one line of /grill-me handed that decision back to me). gpters

To line up with the AI on the goals of his project Lakebed, Theo didn't install the skill. He pasted in the grilling text and handed the job to Claude Opus 5. The AI spent 1 minute 51 seconds reading the repo first, said “I read the repo first so I am grilling from facts, not vibes.” and opened with three findings: the guide file agents read (CLAUDE.md) was badly stale, the repo contradicted its own v0 rule, and it had two competing ways of running things. Theo said, “I'm already realizing that I need to clean up this project.” youtube

Povilas put the description of a market research panel app (Laravel, Filament) into a demo repo and had several approaches plan it. Given the same description, Claude Code's plan mode asked 4 questions, Codex's plan mode 3, and the Superpowers plugin 8. grill-me asked 13. The plan doc grew from 55 lines to 146, but he said “it's not even about the length. It's about the quality of details that are much more ready to start building.” youtube

In August he ran the comparison again, this time on the brief from a real Upwork job he had worked on a few months earlier. Plan mode assumed Filament 4, while grill-me dug further and named Filament 5. But since the update that groups questions into rounds, the first round arrived as nine questions at once, and on his small laptop screen he had to scroll up and down to get through them. youtube