grilling
/grilling
Zadaje użytkownikowi wnikliwe pytania o plan, decyzję lub pomysł, aby sprawdzić myślenie na wytrzymałość.
- Autor
- hachemsoft ↗
- Repozytorium
- ia-toolkit ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zadaje użytkownikowi wnikliwe pytania o plan, decyzję lub pomysł, aby sprawdzić myślenie na wytrzymałość.
Wyzwalacze z opisu
Oryginalny opis (EN)
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Jak działa
SKILL.md bez nagłówków drugiego poziomu · 34 linii, 439 słów
Podgląd SKILL.md
--- name: grilling description: Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases. metadata: aikit-default: "true" aikit-version: "1.0.0" aikit-origin: "upstream" aikit-license: "skills/LICENSE-UPSTREAM-MIT" aikit-summary: "Challenge a plan, a decision or an idea through rounds of questions before implementing it." aikit-category: "workflow" --- Interview the user relentlessly until you reach a shared understanding. Map this as a **design tree**: every decision branches into the decisions that hang off it. Work the tree in **rounds**. The **frontier** is every decision whose prerequisites are already settled: the questions you can ask _now_ without guessing at answers you haven't heard yet. Ask the whole frontier in one round: number each question, give its options and your recommended answer. Then wait for the user's answers before the next round. Format a round like so: ``` ❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs> - **A** - <option>: <what it implies> - **B** - <option>: <what it implies> ➡️ <the option you recommend, and why in one line> --- ❓ **Q2** - **<question title>**: <question body> - **A** - <option>: <what it implies> - **B** - <option>: <what it implies> - **C** - <option>: <what it implies> ➡️ <the option you recommend, and why in one line> ``` Every question offers at least two real options, each with what it implies, so the user can choose without asking you to rephrase; a question with a single possible answer is not a decision, state it as an assumption instead. Word each question so "yes" accepts your recommended answer. Stay inside the scope the user set: the plan, or the step in progress. Ask only the decisions this step needs. A decision that can wait (hosting, access, operations, when the step is framing what to build) is not asked: list it under **Later** at the end of the round, one line each, and move on. Each round the user answers reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a _later_ round, not this one. Finding _facts_ is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent to find it; don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report; ask the rest of the frontier now. The _decisions_ are the user's: put each to them and wait. The session is done when the frontier is empty: every in-scope branch of the design tree visited, nothing left silently assumed, the **Later** list handed over. Do not act on it until the user confirms you have reached a shared understanding.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · hachemsoft/ia-toolkit | 92 | MIT |
| nikospavlopoulos/devops-mutant-powers | 100 | MIT |
| RIJUDEVx/agent-skills | 100 | MIT |
| yuan88964/RelayStudio | 100 | MIT |
| SimplySylvia/Claude-Quorum | 100 | MIT |
| FrancoStino/opencode-skills-collection | 100 | MIT |
| cravingmaker/skills | 100 | MIT |
| helmholtzai-consultants-munich/helmholtz-agent-skills | 100 | Apache-2.0 |
| bendrucker/claude | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 2fbad1c47669 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 82workflow-grilling
Zadaje użytkownikowi wnikliwe pytania o plan lub pomysł, żeby sprawdzić jego tok myślenia, zanim podejmie decyzję. - 100grilling-sleek
Dokładnie przepytuje użytkownika o plan, decyzję lub pomysł, gdy chce on sprawdzić swoje myślenie. - 90grill-me
Przepytuje plan, decyzję lub pomysł bez litości, by sprawdzić myślenie przed budową. - 87grill-me
Przepytuje wytrwale użytkownika o plan, decyzję lub pomysł, by sprawdzić jego tok myślenia przed działaniem. - 100ra-grilling
Dopytuje użytkownika o plan, decyzję lub architekturę, aż każda gałąź drzewa projektu zostanie rozstrzygnięta.