222 件 ・ 関連度順
概要と使いどころ
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 phrase -- including German ones such as "grill mich", "grill mich zu diesem Plan" or "zerpflück meinen Plan im Grill-Modus". Entry point for the /grill-me command; can also be invoked directly.
日本語の概要は準備中です。原文の説明を表示しています。
SUPERSEDED by /claudex-loop (formerly /crucible; adds a Phase 0 research/recon pass + rebuilt interview) — prefer that skill unless you explicitly want this one. Two-act plan hardening. ACT 1 (you ↔ Claude) — Claude interviews you relentlessly about a plan or design, one question at a time, recommending an answer for each and exploring the codebase when it can answer itself, until every branch of the decision tree is resolved. ACT 2 (Claude ↔ Codex) — Claude writes the locked plan to PLAN.md and OpenAI Codex adversarially reviews it in a read-only sandbox (VERDICT:APPROVED/REVISE), Claude revises and re-submits to the SAME Codex session until APPROVED or a MAX_ROUNDS cap, then you sign off before any code. Use when the user says "/grill-me-codex", "grill me then have codex review", "grill me and stress-test the plan", "interview me about this plan then get a second model on it", or is about to build something high-stakes (auth, schema, concurrency, migrations, payments) and wants both alignment AND a cross-model sanity check before implementation. Builds on Matt Pocock's grill-me (MIT). For the docs-aware variant use /grill-with-docs-codex; if you already have a plan and want only the Codex review use /codex-review. NOT for reviewing already-written code (use /codex:review) and NOT for trivial changes.
日本語の概要は準備中です。原文の説明を表示しています。
A relentless interview to sharpen a plan or design. Use when the user says "grill me", "grill mich", "grill mich zu diesem Plan", or explicitly invokes /grill-me. Does NOT fire on generic "review this", "poke holes", "stress-test", "devil's advocate" or "critique" phrasing -- for reviewing an already-written artifact (code, PR, paper) use code-review, 3agenten-review, 7phasen-review or caveman-review instead; grill-me interrogates a still-open plan or idea before it is built.
日本語の概要は準備中です。原文の説明を表示しています。
Relentless one-question-at-a-time interview (tappable options with a recommended answer) that sharpens a requirement, business plan, project plan, proposal, or raw idea through conversation, then writes it up as a brief with a glossary and decision log. Use whenever the user wants their thinking stress-tested or pinned down before acting — trigger phrases include "grill me", "grill this", "詰めて", "詰めたい", "壁打ち", "要件を固めたい", "企画を練りたい", "計画を整理したい", "アイデアをぶつけたい", "突っ込んで", "clarify", "質問して", "何が決まってないか教えて", or when the user describes a plan/idea vaguely and asks what to do next. Do NOT use for reviewing a finished document (use a document-review skill) or when the user just wants an answer, not questions.
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 ("grill me", "grill with docs").
日本語の概要は準備中です。原文の説明を表示しています。
計画や設計を練り直したいときに、踏み込んだ質問を重ねるインタビューを行うスキル。考えを具体化するための対話を、関連スキルの呼び出しで始めます。
SUPERSEDED by /claudex-loop (formerly /crucible; its docs-aware mode covers this variant) — prefer that skill unless you explicitly want this one. Two-act plan hardening with living documentation. ACT 1 (you ↔ Claude) — Claude interviews you relentlessly about a plan, one question at a time, challenging it against your project's existing domain model and glossary (CONTEXT.md), sharpening fuzzy terms, stress-testing with concrete scenarios, cross-referencing code, and updating CONTEXT.md + ADRs inline as decisions crystallise. ACT 2 (Claude ↔ Codex) — Claude writes the locked plan to PLAN.md and OpenAI Codex adversarially reviews it in a read-only sandbox (VERDICT:APPROVED/REVISE), Claude revises and re-submits to the SAME Codex session until APPROVED or a MAX_ROUNDS cap, then you sign off before any code. Use when the user says "/grill-with-docs-codex", "grill me against the docs then have codex review", "stress-test this against our domain model then get a second model on it", or is about to build something high-stakes in a project with established terminology/ADRs and wants alignment, documentation, AND a cross-model sanity check. Builds on Matt Pocock's grill-with-docs (MIT). NOT for reviewing already-written code (use /codex:review) and NOT for trivial changes.
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user relentlessly about the task plan until reaching a shared understanding, resolving each branch of the question decision tree. Use when the user wants to stress-test a plan, get grilled on their plan, or mentions "grill me" or "grill plan".
日本語の概要は準備中です。原文の説明を表示しています。
Odoo-specific grilling session that stress-tests addon plans, migrations, model/view/security designs, OWL frontend changes, and verification strategy. Use when the user wants to be grilled on an Odoo plan/design, asks to stress-test an addon architecture, or mentions grill me in an Odoo context.
日本語の概要は準備中です。原文の説明を表示しています。
Relentlessly interview the user about THEIR plan or design — one question at a time — resolving each branch of a decision tree until shared understanding. Claude is the interviewer; the user is the interviewee. Triggers on "grill me", "stress-test this plan", "get grilled on my design", "interrogate my plan". Checkpoints every answer to docs/knowledge/<slug>.md so progress survives a context-window reset. Flags knowledge the user cannot answer as a gap to chase. Do NOT use to PROPOSE solutions or compare approaches (→ mk:brainstorming). Do NOT use to validate "is this worth building?" (→ mk:office-hours). Do NOT use when Claude should ANSWER questions about the repo (→ mk:ask-me). Do NOT use for a one-shot review of an existing plan (→ mk:plan-ceo-review). Do NOT use to apply named reasoning lenses to findings (→ mk:elicit).
日本語の概要は準備中です。原文の説明を表示しています。
計画やアイデアを質問で掘り下げ、決定同士の依存関係を整理します。推奨案を添えた質問を段階的に重ね、曖昧な前提や未決事項を確認して共通理解を築くスキルです。
仕事や暮らしの繰り返し作業を質問で掘り下げ、開始条件や人の確認、判断用の要約を整理して、実装担当が追加質問なしで作れるワークフロー仕様にするスキル。
Augment a Wren project with business context that DB schema cannot carry — enum value meanings, units (USD vs cents, ms vs sec), NULL semantics, magic sentinels (-1 = unknown), soft-delete default filters, business synonyms, time-grain / TZ conventions, cross-system identifiers, currency rules, canonical-table preferences, AND named aggregation metrics (ARR, churn, DAU, WAU, NRR) proposed as cubes. Runs in one of two modes selected at session start: `grill` (one question at a time, user-driven) or `auto-pilot` (agent infers and applies, escalates only on conflicts and high-blast-radius additions like new cubes / views / relationships). Reads everything under <project>/raw/ (PDFs, glossaries, handbooks, code, data dictionaries) and optionally samples low-cardinality columns from the live DB (grill mode), compares against the current MDL / cubes / knowledge (rules + NL→SQL pairs), then fills gaps via the ten-category gap catalog and the cube proposal flow. Confirmed findings are written back to the right sink. Use when: user says 'enrich context', 'augment my project', 'grill me on this project', 'auto-fill my context', 'agent doesn't understand our docs / enum values / units / null meanings', 'business context is missing', 'what does status=A mean', 'is this amount in USD or cents', 'we keep getting wrong aggregations', 'add cubes for ARR / DAU / churn', 'we have a handbook / glossary / data dictionary the agent should know'; or after generating an MDL and noticing the agent lacks business semantics.
日本語の概要は準備中です。原文の説明を表示しています。
针对方案或设计的高强度追问式面试（adversarial design review / grill session），暴露假设漏洞与缺失约束，过程中同步维护领域模型（术语表和 ADR）。手动调用 /grill-me。
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user relentlessly about a plan, design, or topic, checkpointing every answer to a brainstorm file so nothing is lost. Use when the user wants to stress-test a plan, get grilled on a design, run a brainstorm or discovery session, extract what's in their head into a doc, build up their AI OS context over time, or says "grill me".
日本語の概要は準備中です。原文の説明を表示しています。
Calibrated interrogation of a fuzzy idea before it becomes a spec. Asks one question at a time, recommends an answer, and lands each answer in §G (goal) or §C (constraints) — unknowns parked as `?` items, never guessed. The cheapest place to kill a bad idea is before §T exists. Triggers when the user has a vague idea, says "grill me", "stress-test this", "challenge my plan", "interview me before I spec", or invokes /ck:grill. Defers the actual write to the spec skill.
日本語の概要は準備中です。原文の説明を表示しています。
Génération de sujets d'entraînement complets pour l'épreuve de NOTE DE SYNTHÈSE (5 heures, coefficient 3) de l'examen d'accès au CRFPA : choix du sujet, dossier documentaire de 16 à 20 documents assemblé à partir de sources réelles vérifiées (textes, jurisprudence, travaux parlementaires, doctrine) avec contrôle du verbatim, puis grille de notation au modèle de la Commission nationale (résumé de chaque document, problématique, thèmes cotés sur 20, plan). Livraison en deux fichiers .docx distincts, le sujet et la grille. Si l'utilisateur n'impose pas de sujet, en chercher un dans l'actualité juridique. Mode aveugle pour l'étudiant qui compose sans rien voir du corrigé. Déclencher dès que l'utilisateur demande un sujet de note de synthèse, un dossier documentaire, une note de synthèse blanche, un entraînement à l'épreuve de 5 heures du CRFPA ou de l'IEJ, ou une grille de note de synthèse. NE PAS déclencher pour les épreuves de 3 heures (sujet-crfpa-toutes-matieres) ni pour la correction de copies.
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
日本語の概要は準備中です。原文の説明を表示しています。
资深产品经理助手，提供 PRD/MRD/BRD 创作与评审、产品策略、留存增长、竞品分析、功能优先级，以及 grill-me-to-doc 逐轮访谈。用户要求“逐个问我”“先把需求问清楚”“grill me”“把想法变成产品文档”时进入 grill-me-to-doc：先读仓库证据，每轮只问一个决策，给推荐答案与理由，记录决策和未决项，支持 resume，产出结构化 PRODUCT-DOC；文档完成且用户批准前硬停止，任何时候都不写实现代码。即使未提“产品”，讨论 App 功能、增长或商业模式也应触发。不用于：单纯代码实现、系统架构深设（用 solution-architect）、需多源引用的市场调研（用 deep-research）、纯营销文案。
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。