217건 · 관련도순
Examine business assumptions behind revenue forecasts, market estimates, or hiring plans. Identify counter-evidence, model worse outcomes, assess how changes affect results, and propose validation steps, backup plans, and early warning indicators.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Adversarially stress-tests a legal text — a contract, statute, regulation, or judicial opinion — for interpretive ambiguity: it finds the seams where the people governed by it will later disagree about what it means and turns each into a concrete dispute scenario with both sides' arguments, the likely outcome, and a fix. Use it whenever someone wants to pressure-test, red-team, audit, or find weak spots, loopholes, gaps, ambiguities, or drafting problems in a legal document; whenever a drafter wants to tighten a contract, statute, regulation, or opinion before it issues; whenever a litigator wants to mine an opinion or contract for arguments; or whenever someone hands over a legal text and asks where it will be fought over or for issue-spotting. Trigger it for contract review, statutory-ambiguity analysis, judicial-opinion scope analysis, and drafting QA — even if the user never says "stress-test" or "ambiguity."
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
질문으로 계획과 아이디어를 검토하고 결정 간 의존 관계를 정리합니다. 권장 답변을 담은 질문을 단계적으로 제시해 모호한 전제와 미결 사항을 확인하고 공통 이해를 쌓습니다.
막연한 아이디어를 대화로 구체화하고 여러 안을 비교해 실행 가능한 구상으로 정리합니다. 대상, 성공 기준, 검증할 가정, 최소 범위와 제외할 일도 명확히 합니다.
Stress-test research plans by comparing possible scenarios, such as sample losses, unavailable materials, or methods failing to transfer. Record assumptions and evidence, compare response options, and define contingency plans and observable triggers for changing course.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Estimate private equity deal returns across purchase prices, borrowing levels, growth assumptions, exit prices, and holding periods. Produce Excel sensitivity tables showing annualized returns and investment multiples, plus scenario comparisons and a one-page investment committee summary.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Stress-test ideas, strategies, and plans by breaking them into individual claims for parallel expert agents to challenge. Receive the strongest supporting case, surviving counterarguments, and findings ranked by severity with suggested ways to address weaknesses.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Stress-test a paper with a focused rejection argument, then have a separate reviewer assess each objection against the current text. The report identifies unresolved weaknesses, their severity, and priority fixes for submission or rebuttal preparation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Have Claude and GPT critique each other's answers, revise their positions, and work toward a combined response. Choose the number of rounds and see what changed, where they agree, and which disagreements remain.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Examine a plan or design through focused questions, each with a recommended answer. Work through connected decisions to reach shared understanding, using codebase exploration to resolve questions that the code can answer.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stress-test a finding against the choices you did not make. Enumerates the discrete forks a competent analyst could have taken (measure definition, sample filter, control set, clustering level, weighting, functional form), runs the specification grid, and reports the distribution rather than a point estimate — then attacks the identifying assumption with named, computable sensitivity statistics. Use when the user says "is this robust", "challenge this result", "specification curve", "multiverse", "how sensitive is this", "what if I'd used a different measure", "stress-test my estimate", or before a result becomes a headline claim. NOT a reviewer of prose or code — it challenges the CLAIM.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn an interpretive-ambiguity audit of a legal text — contract, statute, regulation, or judicial opinion — into a polished deliverable. Produces a multi-page website (default), a single-page interactive site, a Microsoft Word document, a PowerPoint deck, or a LaTeX/PDF. Use whenever a user has a stress-test result, ambiguity audit, or "where will this be litigated" scenarios and wants to publish, present, or share them. Triggers on "publish the audit," "make a report from this," "turn this into a website / deck / brief / Word doc," "make a Netlify site," "build slides of these ambiguities," "render the scenarios," "package this stress test," "produce a LaTeX version," and similar. Pairs with the ambiguity-stress-test skill (the underlying analysis) but works on any structured or semi-structured ambiguity analysis. Visual design is opinionated but the user can override colors, fonts, and brand label. Most formats need Python and a writable filesystem; single-file HTML works where the host has neither.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Calibrated grilling session for stress-testing a plan, design, idea, or decision. First assesses the user's topic knowledge, confidence, and desired pressure level, then asks one question at a time with recommended answers. Use when user says "grill me", "stress-test this", "challenge my plan", "interview me", or wants a plan probed without being overwhelmed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my 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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Devil's Advocate stress-testing for code, architecture, PRs, and decisions. Surfaces hidden flaws through structured adversarial analysis with metacognitive depth. Use for high-stakes review, stress-testing choices, or when the user wants problems found deliberately. NOT for routine code review. Triggers on "스트레스 테스트", "stress test", "devil's advocate", "반론", "이거 괜찮아", "문제 없을까", "깊은 리뷰", "critical review", "adversarial".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explicit-only interview loop for stress-testing a plan, decision, or idea. Use only when the user asks to grill, interrogate, interview, or stress-test their thinking before action.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-phase dialectical stress-test for HIGH-STAKES decisions only (architecture choices, irreversible product calls, strategic bets). Heavy-cost skill — do NOT use for routine questions, brainstorming, or simple tradeoffs. User must explicitly invoke or describe a decision they call "high-stakes", "irreversible", or "needs stress-testing". Triggers: "stress test this decision", "dialectic on", "challenge this thesis", "should I really".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설계와 구현의 중요한 결정을 작업 이력을 공유하지 않는 별도 검토자에게 검증받습니다. 숨은 전제와 실패 조건을 찾아 수정하거나 결정을 재검토합니다.