「stress-test」の検索結果

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.

日本語の概要は準備中です。原文の説明を表示しています。

Use when reviewing, critiquing, or stress-testing an existing strategy document. Evaluates seven dimensions — diagnosis quality, guiding policy strength, action coherence, assumption exposure, falsifiability — with optional 7S, Five Forces, Balanced Scorecard, and Hoshin Kanri lenses. Triggers on: review my strategy, poke holes in this plan, what's weak here, strategy audit, red team this. Does NOT build strategy (use strategy-interview) or brainstorm project ideas (use brainstorm-beagle).

日本語の概要は準備中です。原文の説明を表示しています。

A C-level strategy advisory board, run as a team of named specialist agents, that takes an executive from a raw strategic question to a defended, board-ready recommendation. Use this skill whenever the user faces a significant business decision or wants strategic analysis — market entry, build-vs-buy, M&A, digital transformation, annual planning, portfolio prioritization, pricing, a big investment, a competitive threat, a turnaround. Trigger on requests like "should we invest in / build / buy / enter…", "develop a strategy for…", "evaluate this opportunity", "make the business case", "stress-test this plan", "run a pre-mortem", or "prepare a board presentation" — in any language, even when the user doesn't say the word "strategy". Also trigger when the user names a board member (Drucker, Porter, Christensen, Graham, Grove, Wack, Taleb, Minto) or asks to convene the board / open a boardroom session.

日本語の概要は準備中です。原文の説明を表示しています。

Interviews a researcher in rounds until an idea, design, or draft has no unexamined decision — numbered questions, each with why it matters and a recommended answer, facts looked up rather than asked, and settled decisions written to a file. Stages are idea (topic or hunch to a falsifiable question and contribution claim), design (estimand, identification, sample and power, measurement, analysis plan, pre-registration, venue), and defend (reviewer objections to a finished design or draft). Use when the user says "grill me", asks to stress-test or poke holes in an idea, design, or plan, asks what they are assuming, or brings an idea that is not yet a design. --plan grills software or process plans.

日本語の概要は準備中です。原文の説明を表示しています。

Interviews a researcher in rounds (idea, design, or defend stage) until no decision in a research idea, design, or draft is left assumed, recommending an answer to each question and writing settled decisions to a file. Use for 'grill me', stress-testing a design, or an idea not yet a design; --plan for software or process plans.

日本語の概要は準備中です。原文の説明を表示しています。

Grill the user about a requirement, decision, or idea before implementation, then produce an actionable planning report without writing code. Use when the user wants to clarify requirements, stress-test an idea, compare approaches, or plan before coding.

日本語の概要は準備中です。原文の説明を表示しています。

Generate adversarial inputs, edge cases, and boundary test payloads for stress-testing LLM robustness

日本語の概要は準備中です。原文の説明を表示しています。

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".

日本語の概要は準備中です。原文の説明を表示しています。

Two-layer funnel audit on collected data only — stress-test the awareness layer (hooks, messaging, proof placement, attention leaks on live pages and ads) and the lead-capture layer (opt-ins and lead magnets scored on the four Value Equation variables, friction findings, weakest-magnet rewrite), plus a phone-path check under the Phone Capture Fit Rule. Use when "funnel audit", "audit my funnel", "why is my funnel leaking", "top of funnel isn't converting", "audit our lead magnets", "opt-in audit", "awareness to lead audit", "where are we losing people", "lead capture audit", or any request to diagnose the full awareness-to-lead flow rather than one page.

日本語の概要は準備中です。原文の説明を表示しています。

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against their project's language and documented decisions.

日本語の概要は準備中です。原文の説明を表示しています。

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me" outside an Odoo-specific context.

日本語の概要は準備中です。原文の説明を表示しています。

Simulate rigorous, fair peer review on a paper — in two modes. (A) Red-team YOUR OWN draft before submission to predict the reviews you'll get and get a fix list. (B) Review SOMEONE ELSE'S paper when you're an assigned reviewer or helping your advisor — produce a fair, venue-formatted, submission-ready review. Use whenever the user gives a paper (PDF, .tex, .md, arXiv link, or pasted text) and wants to predict reviews, find weaknesses before reviewers do, stress-test a submission, OR write a real review of another paper. Grounded in official NeurIPS/ICLR/ACL reviewer guidelines; every criticism pinned to a location, and checked against ACL's H1–H17 list of illegitimate critiques. 两种模式:审自己的稿(投稿前红队)/ 审别人的稿(当审稿人或帮导师),按会议官方标准评,绝不脑补、绝不发不正当批评。

日本語の概要は準備中です。原文の説明を表示しています。

Test a half-formed idea in a questioning conversation, with different personas probing its weak points, until the user can act on it or drop it with confidence. Optionally writes a short brief for planning skills to build on. Use when the user says 'forge an idea', 'pressure-test this idea', 'stress-test my thinking', or 'harden this idea'

日本語の概要は準備中です。原文の説明を表示しています。

Calculates borrower debt capacity with cash flow coverage, leverage multiples, and stress-tested servicing ability. Use when sizing debt facilities, analyzing leverage capacity, or determining optimal capital structure.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews startup financial models for investor readiness: validates unit economics, stress-tests runway scenarios, and benchmarks metrics against stage-appropriate targets. Use the full review, about 10–15 minutes, when the user provides a financial model (Excel, CSV, or a model pasted as text) and asks for review, validation, runway analysis, or unit-economics scoring. For a single money question with figures to compute, such as 'how long do I have?' or 'is a 4x burn multiple bad?', use its shorter quick check, so the answer comes from the calculator and dated benchmarks, not mental arithmetic.

日本語の概要は準備中です。原文の説明を表示しています。

Builds credible TAM/SAM/SOM analysis with external validation and sensitivity testing for startup fundraising: top-down, bottom-up, or both. Use when the user asks to size a market or check market claims and gives something to size: a product or service description, a market segment, or a deck with TAM/SAM/SOM claims. A full run takes about 15–20 minutes and searches the web, 30 or more with a large data room or a revision round, so for a passing question about market size, answer briefly in chat and offer the analysis instead of starting it. When it runs, every figure is externally sourced and stress-tested, never estimated from memory.

日本語の概要は準備中です。原文の説明を表示しています。

Use when stress-testing a proposal, plan, architecture or decision before committing to it, such as pre-mortems, assumption audits, "should we even do this?" questions, or when everyone agrees too easily. Not for code review; it challenges strategy, approach and hidden risks.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants adversarial stress-testing of a proposed architecture, structure, or shape. Not for tasks that require source or remote-system changes.

日本語の概要は準備中です。原文の説明を表示しています。

Stress-test a design decision with premortem/backcast analysis, then produce a risk-calibrated recommendation that maps to ADR fields. Use when: (1) Multiple competing architecture options, (2) Irreversible or high-risk design choices, (3) /discuss identifies a complex trade-off

日本語の概要は準備中です。原文の説明を表示しています。

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me". Run BEFORE /claude-setup:build when a feature idea is fuzzy and a PRD doesn't yet exist.

日本語の概要は準備中です。原文の説明を表示しています。

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against the project's language and documented decisions. Run BEFORE /build on non-trivial features in repos that have (or should have) a CONTEXT.md.

日本語の概要は準備中です。原文の説明を表示しています。

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against the project's language and documented decisions. Run BEFORE /claude-setup:build on non-trivial features in repos that have (or should have) a CONTEXT.md.

日本語の概要は準備中です。原文の説明を表示しています。

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me". Run BEFORE /build when a feature idea is fuzzy and a PRD doesn't yet exist.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。