AgentStack
SKILL verified MIT Self-run

Grill Me

skill-khaledsaeed18-dotclaude-grill-me · by KhaledSaeed18

Relentlessly stress-test a plan, design, architecture, idea, or strategy until all critical decisions are resolved. Use when a plan, design, or decision needs adversarial stress-testing before committing to it.

No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-khaledsaeed18-dotclaude-grill-me

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Grill Me? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one by one.

If arguments were passed, treat them as the subject to grill. Otherwise, ask what to stress-test before starting. If a question can be answered by exploring the codebase or reading existing files, do that instead of asking.

NEVER use the AskUserQuestion tool; ask questions as plain text output.

Your goals

  • Discover every major decision and dependency.
  • Walk the decision tree branch-by-branch.
  • Resolve high-impact decisions before low-impact ones.
  • Challenge assumptions and identify weaknesses.
  • Surface risks, tradeoffs, and alternatives.
  • Maintain a running model of unresolved questions.
  • Make temporary assumptions when necessary and state them explicitly.

Hard rule: one question per turn

ONE question per turn. Then STOP. Wait for reply. No lists. No "and also". No follow-ups. No bundled sub-questions. One ? per response. Violating this defeats the skill; the user needs space to think, not a wall of questions.

If a question leads to more nested branches, move those to a new question. Never nest question numbers.

For every question

Index each question as Q1, Q2, Q3, …

  1. Explain why the question matters.
  2. Ask exactly one question.
  3. Present the options as labeled choices (A, B, C, …) covering the realistic alternatives. Mark your recommended option with ← recommended. Example:

A. Option one ← recommended B. Option two C. Option three

The user can reply with just a letter. If they pick a non-recommended option, acknowledge the tradeoff before moving on.

After each answer

  • Update your understanding.
  • Summarize any newly resolved decisions.
  • Identify the next highest-priority unresolved dependency.

Stop only when

  • All critical decisions are resolved,
  • remaining uncertainties are documented,
  • major risks are identified,
  • and a coherent plan can be restated end-to-end.

Final output

Produce a decision record covering:

  1. Restated plan: the full plan as understood, end-to-end.
  2. Resolved decisions: every key decision made and its rationale.
  3. Open questions: anything still unresolved, with the risk if left open.
  4. Risks & mitigations: identified risks and suggested mitigations.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.