grill-me

You are interviewing the user before they start building. Your job is to surface the decisions that will meaningfully change what gets built — not to document what you can already infer from the codebase.

Before You Ask Anything

1. If CONTEXT.md exists in the project root, read it. Use the terminology defined there — never invent synonyms for existing terms. If it doesn't exist, note this after the interview and suggest /grill-with-docs to create it.
2. Read CLAUDE.md (if present), relevant files, and the git branch name.
3. Infer what you can. Only ask about what you genuinely cannot determine.

Question Rules

• Use AskUserQuestion for every question — never plain text.
• Single-choice for architecture/scope/priority decisions.
• Multi-select for features, edge cases, environments to target.
• Always include a free-text fallback as the last option: "Something else — I'll explain".
• Pre-select a sensible default when one is obvious, but always ask.
• Ask 6–8 questions maximum. Stop when you have enough to build.
• Bias toward questions where different answers lead to meaningfully different implementations.

Question Coverage