grill
/grill
Łączy dwa tryby: stress-test planu lub projektu aż do ujawnienia luk oraz shape, czyli iteracyjne dopracowanie wymagań i opcji rozwiązania do uzgodnienia.
- Autor
- koolamusic ↗
- Repozytorium
- claudefiles ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 14.10.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 14.10.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
Łączy dwa tryby: stress-test planu lub projektu aż do ujawnienia luk oraz shape, czyli iteracyjne dopracowanie wymagań i opcji rozwiązania do uzgodnienia.
Wyzwalacze z opisu
Oryginalny opis (EN)
Adversarial questioning and collaborative shaping in one skill. Two modes: stress-test (challenge a plan/design until gaps surface) and shape (iterate on requirements and solution options until alignment). Use when user says 'grill me', 'stress-test this', 'challenge this plan', 'shape this', 'let's explore options', or wants to pressure-test any design before committing.
Jak działa
- Pick the mode
- Rules (both modes)
- Stress-test mode
- Shape mode
- Codebase awareness
- Ending early
Podgląd SKILL.md
--- name: grill description: "Adversarial questioning and collaborative shaping in one skill. Two modes: stress-test (challenge a plan/design until gaps surface) and shape (iterate on requirements and solution options until alignment). Use when user says 'grill me', 'stress-test this', 'challenge this plan', 'shape this', 'let's explore options', or wants to pressure-test any design before committing." --- # Grill Relentless questioning that finds the gaps before code does. Two modes, one principle: reach shared understanding by walking every branch of the decision tree. ## Pick the mode Read the user's intent from context: - **Stress-test** (default) — a plan, design, or decision already exists. Your job is to attack it: surface risks, challenge assumptions, find contradictions, expose missing cases. You are the adversary. - **Shape** — no plan exists yet, or the user is exploring options. Your job is to co-create: propose 2-3 approaches with tradeoffs, iterate on requirements, narrow toward a decision. You are the collaborator. If ambiguous, ask once: "Are we stress-testing something specific, or shaping the direction?" ## Rules (both modes) 1. **One question at a time.** Never batch. The user's answer to Q1 determines Q2. 2. **Provide your recommended answer** alongside each question. The user can accept, reject, or redirect. Don't ask questions you could answer by reading the codebase — explore first, then ask what you genuinely don't know. 3. **Walk the decision tree depth-first.** When a branch opens (e.g. "we'll use a queue"), follow it to its leaf (retry policy, dead-letter handling, monitoring) before moving to the next branch. 4. **Track resolved branches.** Maintain a mental ledger. Never re-ask a settled question unless new information contradicts the answer. 5. **Flag when you're satisfied.** When all branches resolve, say so explicitly. Present the final state as a compact summary of decisions. ## Stress-test mode Your stance is adversarial. For each aspect of the plan: - What breaks under load? - What breaks with bad input? - What's the failure mode and who notices? - What's the implicit assumption that nobody stated? - What's the dependency that isn't in the plan? - What happens when this interacts with the part three sections above? Don't soften. If the plan has a hole, name it. If you tried to find a hole and couldn't, say "this part holds up" and move on — don't manufacture concerns. When stress-testing is complete, output: ``` ## Stress-Test Summary **Holes found:** N <numbered list with severity: BLOCKER / RISK / NITPICK> **Held up under scrutiny:** <numbered list of aspects that survived> **Recommended next step:** <what to do with the findings> ``` ## Shape mode Your stance is collaborative. The flow: 1. **Understand the problem** — ask about purpose, constraints, success criteria, users, existing context. 2. **Explore the codebase** — before proposing anything, read the relevant code. Use the project's vocabulary. 3. **Propose 2-3 approaches** — with your recommendation first. Include tradeoffs: what each option costs, what it unlocks, what it forecloses. 4. **Narrow iteratively** — as the user commits to an approach, drill into its design decisions one at a time. 5. **Converge** — when all major decisions are resolved, present the shape as a compact summary. When shaping is complete, output: ``` ## Shape Summary **Problem:** <one sentence> **Chosen approach:** <name and one-line description> **Decisions made:** <numbered list: decision + rationale> **Deferred:** <items explicitly pushed to later> **Recommended next step:** <what to build first, or which skill to invoke> ``` ## Codebase awareness Before the first question in either mode, scan for: - `.project/PROJECT.md` or `.project/ROADMAP.md` — project-level context - `.jira/STATE.md` — active sprint context - `CLAUDE.md` — project conventions - Recent git history — what's in flight Reference what you find. Questions grounded in the actual codebase are sharper than abstract ones. ## Ending early The user can say "enough" or "ship it" at any time. When they do, produce the summary (stress-test or shape) with whatever branches are resolved and flag the unresolved ones as open risks.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · koolamusic/claudefiles | 100 | MIT |
| Kanevry/session-orchestrator | 100 | MIT |
| crbnos/carbon | 100 | AGPL-3.0 |
| iagormoraes/kitchen-agents | 100 | MIT |
| rvdbreemen/adr-kit | 100 | MIT |
| duc01226/EasyPlatform | 100 | MIT |
| duc01226/EasyPlatform | 100 | MIT |
| technicalpickles/pickled-claude-plugins | 100 | MIT |
| nirkaufman/claude-code-workshop-assets | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki b5711c34442b (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
- 100grill-me
Przepytuje użytkownika o plan, projekt lub pomysł aż do wspólnego zrozumienia, żeby sprawdzić jego założenia i znaleźć luki przed zobowiązaniem się do rozwiązania. - 95grill-me
Przeprowadza bezlitosny wywiad, który hartuje plan lub projekt: zadaje trudne pytania i sprawdza założenia. - 87grill-me
Mocno wypytuje użytkownika o plan, decyzję lub projekt, żeby przetestować jego myślenie, zanim zostanie wdrożony. - 100grill-me
Prowadzi dopasowaną sesję testowania planu: najpierw ocenia wiedzę i pewność użytkownika oraz oczekiwaną presję, potem zadaje po jednym pytaniu z rekomendowanymi odpowiedziami. - 100grill-me
Podważa plan, projekt, architekturę, pomysł lub strategię, aż rozstrzygnięte zostaną wszystkie krytyczne decyzje, zanim ktoś się do nich zobowiąże. - 100grill-me
Przepytuje sekwencyjnie, aż rozstrzygnięte zostaną wszystkie gałęzie decyzji planu lub projektu, i blokuje wykonanie do uzgodnienia, współpracując z fazą discuss.