27 lines
1.8 KiB
Markdown
27 lines
1.8 KiB
Markdown
---
|
|
name: grill-me
|
|
description: >-
|
|
Relentlessly interview the user to stress-test a plan, requirement, or architectural
|
|
choice before writing code or selecting a solution. Activate this skill when the user
|
|
asks to "grill me", clarify requirements, align on a design, or choose between technical
|
|
approaches.
|
|
---
|
|
|
|
# Grill Me — Decision-Tree Architecture & Requirement Interview
|
|
|
|
Instead of guessing requirements or dumping a massive, superficial plan, walk the decision tree of the user's idea **depth-first** through structured, high-leverage questions until every critical branch is resolved.
|
|
|
|
## Core Protocol
|
|
|
|
1. **Codebase-First Rule**:
|
|
- Never ask the user a question that the existing codebase or system state (`GEMINI.md`, repository files, running services) can already answer. Check the codebase first.
|
|
2. **Model the Decision Tree**:
|
|
- Break the problem into **Top-Level Branches** (core user workflow, primary goal, deployment boundary), **Sub-Branches** (trade-offs, UX expectations, integration points), and **Leaf Nodes** (implementation details).
|
|
3. **Depth-First & Frontier Questioning**:
|
|
- Ask **1 to 3 sharp, high-leverage questions per round** using the `ask_question` tool (when available) or structured multiple-choice options.
|
|
- Do not ask about downstream implementation details before upstream workflow decisions are settled.
|
|
4. **Always Provide a `(Recommended)` Option**:
|
|
- Every question MUST put a well-reasoned recommended answer first, prefixed with `(Recommended)`, explaining *why* it fits the user's architecture best.
|
|
5. **Converge to a Concrete Decision Record**:
|
|
- Once the critical branches of the decision tree are resolved, synthesize the locked-in decisions into a concise execution plan and ask for final confirmation to build/deploy.
|