agentsclimarketplace

Grill

Skill fortunto2/solo-factory/skills/grill

Relentless one-question-at-a-time interview that stress-tests a plan, design, or decision before anything gets built. Use when user says "grill me", "прожарь", "разбери мою идею", "stress-test this", "punch holes in this", or a plan still has soft spots. Also reachable by other skills that need an interview. Do NOT use for scoring an idea (/validate) or writing the implementation plan (/plan).From its SKILL.md

Install
npx -y skills add fortunto2/solo-factory --skill grill

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, as published. Nobody here has run it

/grill — the interview primitive

Interview the user relentlessly about every aspect of the thing until you reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one by one. For each question, give your own recommended answer.

Ask one question at a time, waiting for the answer before the next. A batch of questions is bewildering and destroys the dependency order that makes the interview converge.

Look up facts; ask for decisions. If something can be settled by exploring the environment — filesystem, git history, the codebase, the web — go and settle it. The decisions are the user's: put each one to them and wait.

Do not act on the plan until the user confirms the shared understanding is reached.

Why one at a time

The mental model is a decision tree. An early answer reshapes which questions come next — a firehose of parallel questions throws away that structure and produces answers to questions that turned out not to matter.

Composing

This is a primitive, not a workflow. Reach for it from inside other work whenever a plan needs sharpening:

  • Before /plan — when the feature is still fuzzy. /plan deliberately asks zero questions and researches code instead, so grill first when the decisions, not the code, are what's missing.
  • Before /validate — when the idea itself hasn't been pinned down enough to score.
  • Inside /stream — when a STREAM layer needs the user's judgement rather than analysis.
  • After /diagnose Phase 3 — to pressure-test which hypothesis to chase.

Gotchas

  • Recommendations are the point. A bare question makes the user do all the work; a question with your recommended answer lets them correct a draft, which is far faster.
  • Asking what you could look up burns trust. Check the repo, the config, the git log first.

Don't

  • Batch questions "to save time" — it costs more.
  • Start building the moment the user answers the last question; confirm the shared understanding first.

Adapted from grilling by Matt Pocock (MIT, Copyright (c) 2026 Matt Pocock). See THIRD-PARTY.md.

Keep looking

Skills are one crate of 611,178. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.