← ClaudeAtlas

grill-me-mlisted

Interview the user relentlessly about a plan, design, or topic until reaching shared understanding. Walks each branch of the decision tree. Decisions are captured in a distilled brainstorm file (delegated to notes-M). Use when user wants to stress-test a plan, get grilled, run a discovery session, or says "grill me".
MathCaz/claude-skills · ★ 0 · AI & Automation · score 75
Install: claude install-skill MathCaz/claude-skills
# Grill Me Relentlessly interview me about every aspect of the topic until we reach shared understanding. Walk down each branch of the decision tree, resolving dependencies one by one. Goal: extract what's in my head into a durable, organized file. ## File mechanics — delegated to `notes-M` All file operations (create / reopen / structure / checkpoint / curation / status / reconcile) live in the **`notes-M`** skill. Use it in **`interview` mode**. `notes-M` will auto-invoke when it detects a multi-step interview. You don't need to call it explicitly — just follow the interview discipline below, and write each captured decision to the file `notes-M` creates. Body section in the file = `## Decisions log` (see `notes-M` for the consolidated-entry format: Decision · Why · Dead-ends · Flags). ## Question style For each question: - Present **numbered or lettered options** whenever possible so I can reply with just a number, letter, or one word. - For open-ended questions that can't be simplified, mark them clearly as needing more detail. - Provide your **recommended answer** (your best inference from context) so I can just confirm, correct, or redirect. - Minimize my typing — aim for replies of one word, one number, or 1–2 sentences max. ## Question flow - Ask **one question at a time**. Wait for my answer before moving on. - Resolve dependencies in order: settle the upstream decision before ones that depend on it. - If a question can be answered by **reading a file/doc or