Grill Me
- 1 installs
- 3 repo stars
- Updated August 1, 2026
- dimagi/dimagi-claude-workflows
Interviews you one question at a time about a plan or design, resolving every decision branch and recording resolutions in a design document.
About
Systematically interrogates a plan or design until every open question and decision branch is resolved and documented. A developer uses it to stress-test a plan and reach shared understanding before implementation.
- Interrogates a plan one question at a time, never batching questions
- Answers its own questions from the codebase and challenges weak answers
Grill Me by the numbers
- 1 all-time installs (skills.sh)
- Ranked #2,479 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/dimagi/dimagi-claude-workflows --skill grill-meAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 3 |
| Last updated | August 1, 2026 |
| Repository | dimagi/dimagi-claude-workflows ↗ |
What it does
Interviews you one question at a time about a plan or design, resolving every decision branch and recording resolutions in a design document.
Files
Goal
Systematically interrogate every aspect of the user's plan or design until all decisions are resolved and documented.
Process
1. Identify the plan. Ask the user to state their plan, or read it from a file/context they provide. 2. Map the decision tree. Identify all open questions, assumptions, and decision branches. 3. Walk each branch one question at a time. Ask a single focused question, wait for the answer, then move to the next. Never batch multiple questions. 4. Answer your own questions when possible. If a question can be resolved by exploring the codebase (reading files, checking existing patterns, grepping for usage), do that instead of asking the user. State what you found and your conclusion. 5. Track dependencies. If a decision depends on an earlier unresolved one, resolve the dependency first. 6. Challenge weak answers. If the user's answer is vague, contradictory, or hand-wavy, push back with a specific follow-up. 7. Maintain a design document. Record every question and its resolution in a design doc. Update it as you go so the user can see the accumulated decisions.
When to stop
Stop when every branch of the decision tree has a concrete resolution and the user confirms the design document reflects the final plan.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k