「hypothesis-driven」の検索結果

管理咨询 (管理咨询 (Management Consulting) — 战略与管理咨询的职业认知操作系统，从业者/咨询顾问/想入行者/采购咨询服务的客户视角。覆盖: (a) 第一性张力 — 假设驱动 (hypothesis-driven / answer-first / Day-1 answer) 的「先有答案再验证」⇄ 数据驱动 (data-led / bottom-up) 的「先穷尽事实再归纳」，这行的核心张力是「先射箭再画靶 vs 先画靶再射箭」，资深人偏 top-down 假设树减少 boil-the-ocean，但要时刻防 confirmation bias; 以及更深层的张力 — 「卖洞见 (insight / so-what) vs 卖工时 (analysis / 体力)」，「客户影响 (client impact / 落地) vs 智识严谨 (intellectual rigor / 漂亮 deck)」; (b) 方法论正典 (最标准化、最易蒸出高质量) — MECE (相互独立完全穷尽)、issue tree / logic tree (问题树/逻辑树)、hypothesis-driven problem solving (假设驱动)、Pyramid Principle (Minto 金字塔原理: SCQA 情境-冲突-疑问-回答 + 结论先行 + 自上而下 + 归纳/演绎)、80/20 (帕累托/抓大放小)、so-what (所以呢/洞见提炼)、storyline (故事线/ghost deck 鬼影稿)、driver tree / profit tree、2x2 矩阵、value chain、frameworks (Porter 五力/3C/4P/7S/BCG 矩阵/价值链) 既是脚手架也是陷阱 (套框架 vs 真洞见); (c) 行业结构 — MBB (McKinsey/BCG/Bain 战略三巨头) vs Big Four 咨询臂 (Deloitte/PwC Strategy&/EY-Parthenon/KPMG) vs 精品战略所 (Oliver Wyman/Kearney/Roland Berger/L.E.K./Arthur D. Little) vs 专业/职能 boutique (运营/数字化/PE 尽调); up-or-out (非升即走)、leverage model (杠杆模型: 1 个合伙人带多个 EM/咨询师/分析师的金字塔)、partner/principal/EM(项目经理)/associate(咨询师)/analyst(分析师) 职级; (d) 项目交付模型 (the case/study/engagement) — 提案/SOW (scope of work)、problem definition (问题定义/真问题 vs 表象问题)、workplan (工作计划)、hypothesis tree (假设树)、analysis (分析/建模)、synthesis (综合)、recommendation (建议)、implementation (落地); 客户管理 (steering committee 指导委员会、stakeholder 利益相关方、对齐); (e) 产出物 — the deck (PPT 幻灯片是咨询的母语)、executive summary、action title (行动标题/每页一句话结论)、ghost deck (先搭骨架后填数据)、Excel 财务模型、framework 图; (f) 职业/招聘 — case interview 生态 (案例面试: Victor Cheng LOMS/Case in Point/market sizing 市场估算/估算题/fit 行为面)、网申-笔试-案例面、up-or-out、exit options (退出路径: PE/VC/corp dev 企业发展/战略岗/创业/industry); (g) 争议/批判 — 咨询的价值之辩 (「借你的表告诉你时间」「frameworks 是剧场表演 vs 真洞见」Matthew Stewart《The Management Myth》)、McKinsey 的丑闻 (Purdue 阿片类/独裁政府/ICE/利益冲突, Bogdanich & Forsythe《When McKinsey Comes to Town》)、咨询 vs 自建战略部、generalist 通才 vs specialist 专才之争、AI/GenAI 对初级分析师工作的冲击; (h) 流派 — 战略经典 (Porter 定位学派/五力 vs 资源基础观 RBV vs 蓝海战略 Kim&Mauborgne vs 颠覆式创新 Christensen vs Mintzberg 应急战略批判 planning school); 三巨头气质分野 (McKinsey 事实驱动/CEO 信任/通才, BCG 概念/思想领导力/经验曲线/增长-份额矩阵, Bain 结果导向/NPS 净推荐值/PE 关系/与客户深度绑定)。不含: 投行 M&A/财务顾问 (估值/承销超出范畴)、纯 IT 实施/系统集成 (SI 人力外包)、纯审计/税务、纯人力 RPO/猎头、内部战略部 only (虽相关但本 skill 聚焦专业服务咨询的外部视角)。) Master OS — automated mastery of 管理咨询 (Management Consulting) — 战略与管理咨询的职业认知操作系统，从业者/咨询顾问/想入行者/采购咨询服务的客户视角。覆盖: (a) 第一性张力 — 假设驱动 (hypothesis-driven / answer-first / Day-1 answer) 的「先有答案再验证」⇄ 数据驱动 (data-led / bottom-up) 的「先穷尽事实再归纳」，这行的核心张力是「先射箭再画靶 vs 先画靶再射箭」，资深人偏 top-down 假设树减少 boil-the-ocean，但要时刻防 confirmation bias; 以及更深层的张力 — 「卖洞见 (insight / so-what) vs 卖工时 (analysis / 体力)」，「客户影响 (client impact / 落地) vs 智识严谨 (intellectual rigor / 漂亮 deck)」; (b) 方法论正典 (最标准化、最易蒸出高质量) — MECE (相互独立完全穷尽)、issue tree / logic tree (问题树/逻辑树)、hypothesis-driven problem solving (假设驱动)、Pyramid Principle (Minto 金字塔原理: SCQA 情境-冲突-疑问-回答 + 结论先行 + 自上而下 + 归纳/演绎)、80/20 (帕累托/抓大放小)、so-what (所以呢/洞见提炼)、storyline (故事线/ghost deck 鬼影稿)、driver tree / profit tree、2x2 矩阵、value chain、frameworks (Porter 五力/3C/4P/7S/BCG 矩阵/价值链) 既是脚手架也是陷阱 (套框架 vs 真洞见); (c) 行业结构 — MBB (McKinsey/BCG/Bain 战略三巨头) vs Big Four 咨询臂 (Deloitte/PwC Strategy&/EY-Parthenon/KPMG) vs 精品战略所 (Oliver Wyman/Kearney/Roland Berger/L.E.K./Arthur D. Little) vs 专业/职能 boutique (运营/数字化/PE 尽调); up-or-out (非升即走)、leverage model (杠杆模型: 1 个合伙人带多个 EM/咨询师/分析师的金字塔)、partner/principal/EM(项目经理)/associate(咨询师)/analyst(分析师) 职级; (d) 项目交付模型 (the case/study/engagement) — 提案/SOW (scope of work)、problem definition (问题定义/真问题 vs 表象问题)、workplan (工作计划)、hypothesis tree (假设树)、analysis (分析/建模)、synthesis (综合)、recommendation (建议)、implementation (落地); 客户管理 (steering committee 指导委员会、stakeholder 利益相关方、对齐); (e) 产出物 — the deck (PPT 幻灯片是咨询的母语)、executive summary、action title (行动标题/每页一句话结论)、ghost deck (先搭骨架后填数据)、Excel 财务模型、framework 图; (f) 职业/招聘 — case interview 生态 (案例面试: Victor Cheng LOMS/Case in Point/market sizing 市场估算/估算题/fit 行为面)、网申-笔试-案例面、up-or-out、exit options (退出路径: PE/VC/corp dev 企业发展/战略岗/创业/industry); (g) 争议/批判 — 咨询的

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

Conduct proactive, hypothesis-driven threat hunts — search SIEM / EDR / logs for adversaries who haven't tripped an alert yet. ATT&CK-driven, hypothesis-based methodology. Use when the user mentions 'threat hunting,' 'proactive hunt,' 'TaHiTI,' 'PEAK framework,' 'MITRE ATT&CK hunt,' 'hypothesis-driven hunt,' 'hunt hypothesis,' 'living off the land,' 'LOLBins,' 'beaconing,' 'lateral movement detection,' 'data staging,' 'persistence hunting,' or wants to find threats that have evaded existing detections.

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

Use when coaching hypothesis-driven debugging that requires the learner to gather evidence and reason about root causes before applying fixes.

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

This skill should be used when the user wants to "investigate a bug", "debug an issue", "figure out why something is happening", "find the root cause", "troubleshoot", "強い推論で調査", "仮説を立てて検証", "原因を特定", "バグの原因調査", "なぜ動かないか調べて", "問題を切り分け", "原因不明", "デバッグ", or mentions systematic hypothesis-driven debugging. NOTE: Use this for investigating UNKNOWN causes, not for validating design proposals (use devils-advocate for that).

Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles and locking the fix with a failing test. Use for crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior, or reverse engineering.

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

Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't work, when behavior seems "impossible", or when you're tempted to blame an external system (model, API, library) without evidence.

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

Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry. Covers hypothesis-driven threat hunting, IOC sweep generation, z-score anomaly detection, and MITRE ATT&CK-mapped signal prioritization.

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

Expert guidance for deep security incident and entity investigations in Google SecOps. Use when investigating cases, analyzing entities (hosts, IPs, domains, hashes, users), extracting and searching UDM events, performing asset and user timeline analysis, and detecting lateral movement across enterprise networks. Don't use for detection rule authoring or YARA-L tuning (use secops-detection-engineering), proactive hypothesis-driven hunting (use secops-hunt), initial alert triage (use secops-triage), or basic case status updates (use secops-cases).

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

Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis.

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

Expert SRE investigator for incidents and debugging. Uses hypothesis-driven methodology and systematic triage. Can query Axiom observability when available. Use for incident response, root cause analysis, production debugging, or log investigation.

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

Proactive threat hunt over web/application logs — no alert in hand. Profiles the corpus, runs a hypothesis-driven hunt loop with a mandatory written ledger, confirms suspects in source, detonates a local PoC, and writes INCIDENTS.json + INCIDENT_REPORT.md. Use when asked to "hunt the logs", "find the campaign", "look for signs of compromise", or "run dnr-hunt". The no-alert entry to the detection & response track; /dnr-respond is the lead-in-hand entry.

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

Hypothesis-driven, tool-grounded security review of coverage gaps

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

Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles and locking the fix with a failing test. Use for crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior, or reverse engineering.

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

[omh] Native program crashes or corrupts memory: prepare hypothesis-driven debugging of native binaries and instruct the executor to drive a DAP debugger instead of printf. Use when the user says: native-debugging, native debugging, native binary, segfault, segmentation fault, core dump, stack corruption, memory corruption.

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

Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "outcome over output", "design studio method", "assumption mapping", "lightweight research", "too much design documentation", or "get the team designing together". Also trigger when reducing design-documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.

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

Designs primary aims, secondary aims, and testable hypotheses from broad biomedical research ideas. Use this skill when a user needs to convert a loose study idea into a tighter protocol-framing structure with clear aim hierarchy, hypothesis discipline, and separation between hypothesis-driven and exploratory components. Always keep aims answerable, non-overlapping, and aligned to the intended evidence type and study scope.

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

Structured debugging methodology using hypothesis-driven investigation, log analysis, and bisection to isolate and resolve defects.

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

Performs systematic root cause analysis to identify the true source of bugs, errors, and unexpected behavior through structured investigation phases — not just treating symptoms. Use when a user reports a bug, crash, error, or broken behavior and needs to debug, troubleshoot, or investigate why something is not working; especially for complex or intermittent issues across multiple components. Applies the Five Whys method, hypothesis-driven testing, stack trace analysis, git blame/log evidence gathering, and causal chain documentation to isolate and confirm root causes before applying any fix.

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

Run conversion rate optimization through hypothesis-driven testing including audit, hypothesis generation, test design, statistical analysis, and rollout decisions. Use this skill whenever the user wants to optimize conversion, run A/B tests, audit a funnel, generate test hypotheses, design experiments, or analyze test results. Triggers on conversion optimization, CRO, A/B test, split test, multivariate test, hypothesis, conversion funnel, funnel audit, experiment design, statistical significance, lift, optimization. Also triggers when the user has a conversion problem and isn't sure where to start, or when test results are ambiguous and need interpretation.

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

Parses error messages, traces execution flow through stack traces, correlates log entries, and applies systematic hypothesis-driven methodology to isolate and resolve bugs.

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

Chaos engineering: hypothesis-driven fault injection to surface weakness before users do. Use when designing a chaos experiment, planning a gameday, choosing what to inject, computing blast radius, or building a chaos maturity model.

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

Conducts hypothesis-driven, evidence-preserving threat hunts with bounded negative conclusions and telemetry-gap handling. Use for hunt hypotheses, scoped offline analysis, or analytic follow-up; not unscoped scanning, malware execution, or generic intelligence summaries.

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

Validate system resilience through controlled fault injection. Covers hypothesis-driven chaos experiments, failure injection types (network, service, infrastructure, dependency), LitmusChaos/Chaos Mesh/AWS FIS/Gremlin/toxiproxy tooling, automated abort gating, game day planning, and progressive chaos adoption. Use when: "chaos engineering," "fault injection," "resilience test," "game day," "failure recovery," "system reliability," "blast radius." Not for: safe rollout flags/canary/dark launch during a release — use testing-in-production; designing new tests from production telemetry — use observability-driven-testing. Related: testing-in-production, observability-driven-testing, performance-testing, release-readiness, test-environments.

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

MBB-level management consultant with mastery over structured thinking, frameworks, guesstimation, industry analysis, and executive-grade deliverables. Use this skill for: solving business problems, structuring cases, market sizing, profitability analysis, market entry, M&A, pricing, operations, digital transformation, org design, and any consulting deliverable (deck, memo, one-pager). Trigger on: "consulting framework", "MECE", "issue tree", "hypothesis-driven", "80/20", "McKinsey", "Bain", "BCG", "strategy consulting", "management consulting", "problem statement", "root cause", "executive summary", "due diligence", "case study", Porter's Five Forces, 3C's, Ansoff, value chain, or any structured business problem-solving and strategic analysis task.

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