reasoning-counterfactual
Evaluate alternative scenarios by simulating interventions on past decisions or hypothetical futures. Use when assessing decisions in hindsight, planning scenarios, or comparing paths not taken. Produces comparative analysis with probability-weighted outcomes.
下記のコマンドをコピーしてターミナル(Mac/Linux)または PowerShell(Windows)に貼り付けてください。 ダウンロード → 解凍 → 配置まで全自動。
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -L -o reasoning-counterfactual.zip https://jpskill.com/download/17498.zip && unzip -o reasoning-counterfactual.zip && rm reasoning-counterfactual.zip
$d = "$env:USERPROFILE\.claude\skills"; ni -Force -ItemType Directory $d | Out-Null; iwr https://jpskill.com/download/17498.zip -OutFile "$d\reasoning-counterfactual.zip"; Expand-Archive "$d\reasoning-counterfactual.zip" -DestinationPath $d -Force; ri "$d\reasoning-counterfactual.zip"
完了後、Claude Code を再起動 → 普通に「動画プロンプト作って」のように話しかけるだけで自動発動します。
💾 手動でダウンロードしたい(コマンドが難しい人向け)
- 1. 下の青いボタンを押して
reasoning-counterfactual.zipをダウンロード - 2. ZIPファイルをダブルクリックで解凍 →
reasoning-counterfactualフォルダができる - 3. そのフォルダを
C:\Users\あなたの名前\.claude\skills\(Win)または~/.claude/skills/(Mac)へ移動 - 4. Claude Code を再起動
⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。
🎯 このSkillでできること
下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。
📦 インストール方法 (3ステップ)
- 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
- 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
- 3. 展開してできたフォルダを、ホームフォルダの
.claude/skills/に置く- · macOS / Linux:
~/.claude/skills/ - · Windows:
%USERPROFILE%\.claude\skills\
- · macOS / Linux:
Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。
詳しい使い方ガイドを見る →- 最終更新
- 2026-05-18
- 取得日時
- 2026-05-18
- 同梱ファイル
- 1
📖 Skill本文(日本語訳)
※ 原文(英語/中国語)を Gemini で日本語化したものです。Claude 自身は原文を読みます。誤訳がある場合は原文をご確認ください。
反実仮想推論
代替現実をシミュレートします。「もし〜だったら」という論理と意思決定の評価。
型シグネチャ
Counterfactual : Actual → Intervention → Alternative → Comparison
ここで:
Actual : Decision × Outcome → ActualWorld
Intervention : ActualWorld × Δ → ModifiedPremise
Alternative : ModifiedPremise → ProjectedOutcome
Comparison : (ActualWorld, ProjectedOutcome) → DifferenceAnalysis
どのような時に使うか
反実仮想推論は以下の場合に使用します:
- 過去の意思決定の評価(「〜すべきだったか」)
- シナリオプランニング(「もしXが起こったら」)
- 取らなかった選択肢の比較(「もし〜を選んでいたら」)
- 戦略的シミュレーション(「もし競合がXをしたら」)
- 結果からの学習(「私たちの決定は正しかったか?」)
以下の場合には使用しないでください:
- 既知のプロセスの実行 → Causalを使用
- 観察の説明 → Abductiveを使用
- 意見の不一致の解決 → Dialecticalを使用
中核となる原則
最小限の介入
仮説を検証するために必要なことだけを変更します。
- 可能であれば一度に1つの変数を変更します
- 他のすべてを一定に保ちます(ceteris paribus)
- ダウンストリームの影響を注意深く追跡します
確率の重み付け
代替の結果は確実ではありません。
- 予測される結果ごとに確率を割り当てます
- 介入ごとに複数の可能な代替案を検討します
- 予測に過信しないようにします
非対称性の認識
反実仮想分析には固有のバイアスがあります。
- 後知恵は代替案をより明確に見せます
- 生存者は失敗につながった道筋を見ていません
- 予測への信頼は高すぎる傾向があります
4段階のプロセス
ステージ1: 実際の状況 (Actual World)
目的: 行われた意思決定と観察された結果を文書化します。
構成要素:
actual:
decision:
what: "行われた選択"
when: ISO8601
who: "意思決定者"
context: "意思決定時の状況"
alternatives_considered: [string] # 当時
outcome:
result: "実際に起こったこと"
metrics:
- metric: "測定可能な結果"
value: number
expected: number # 予測された値
timeline: "結果までの期間"
assessment:
success_level: high | medium | low | failed
surprise_level: 0.0-1.0 # どれほど予想外だったか
causal_chain:
- step: "意思決定がXにつながった"
- step: "XがYにつながった"
- step: "Yが結果を生み出した"
例:
actual:
decision:
what: "エンタープライズ層の価格を$50K/年とした"
when: "2024-06-01"
who: "創業者"
context: "初のエンタープライズ立ち上げ、市場データなし"
alternatives_considered:
- "$30K/年(より低い障壁)"
- "$75K/年(より高いマージン)"
- "使用量ベースの価格設定"
outcome:
result: "6ヶ月で3件の契約を締結、$150K ARR"
metrics:
- metric: "契約数"
value: 3
expected: 5
- metric: "ARR"
value: 150000
expected: 250000
- metric: "販売サイクル"
value: 120 # 日
expected: 90
timeline: "6ヶ月"
assessment:
success_level: medium
surprise_level: 0.4 # 予想をやや下回る
causal_chain:
- step: "$50Kの価格設定"
- step: "5件の見込み客のうち3件がこのレベルでCFOの承認を必要とした"
- step: "CFOの承認によりサイクルに30日が追加された"
- step: "2件の契約が予算サイクルのタイミングで失われた"
ステージ2: 介入 (Intervention)
目的: 評価する代替の意思決定を定義します。
介入の種類:
| Type | Description | Example |
|---|---|---|
| Price | 異なる価格設定の決定 | "$50Kの代わりに$30K" |
| Timing | より早いまたは遅い行動 | "3ヶ月早く立ち上げた" |
| Strategy | 異なる戦略的選択 | "エンタープライズの代わりにSMBファースト" |
| Resource | 異なる割り当て | "より早く営業担当者を雇用した" |
| Partner | 異なる関係 | "Yの代わりにXと提携した" |
構成要素:
intervention:
what: "代替の選択"
change:
variable: "変更されるもの"
from: "実際の値"
to: "代替の値"
rationale:
why_consider: "この代替案を評価する価値がある理由"
was_available: bool # 当時、これは実際に選択肢でしたか?
assumptions:
held_constant:
- "同じままであると仮定するもの"
ripple_effects:
- "予想されるダウンストリームの変更"
例:
intervention:
what: "$50K/年の代わりに$30K/年で価格設定"
change:
variable: "エンタープライズ層の年間価格"
from: "$50,000"
to: "$30,000"
rationale:
why_consider: "低価格が速度を上げるかどうかをテストする"
was_available: true # これは当時検討された
assumptions:
held_constant:
- "同じ製品機能"
- "同じ営業チーム"
- "同じ市場状況"
- "同じターゲット顧客プロファイル"
ripple_effects:
- "異なる承認しきい値(マネージャー対CFO)"
- "潜在的に異なる顧客の期待"
- "1件あたりのマージンが低い"
ステージ3: 代替案の予測 (Alternative Projection)
目的: 介入の下で何が起こったかを予測します。
予測方法:
- 意思決定ポイントを特定する - パスが分岐する場所
- 因果連鎖を追跡する - ダウンストリームで何が変わるか?
- 結果を推定する - 確率の重み付けを使用
- 複数のシナリオを検討する - ベスト/ワースト/予想
構成要素:
alternative:
scenarios:
- name: "予想されるケース"
probability: 0.6
outcome:
deals: 6 # 実際の3件と比較
arr: 180000 # 実際の150000と比較
cycle: 75 # 日、実際の120日と比較
reasoning: "低価格 = より迅速な承認、より多くの契約、ただし1件あたりの金額は低い"
- name: "楽観的なケース"
probability: 0.25
outcome:
deals: 8
arr: 240000
cycle: 60
reasoning: "ボリューム効果が予想以上に強い"
- name: "悲観的なケース"
probability: 0.15
outcome:
deals: 4
arr: 120000
cycle: 90
reasoning: "低価格は低い価値を示唆し、一部の見込み客は躊躇する"
weighted_ou 📜 原文 SKILL.md(Claudeが読む英語/中国語)を展開
Counterfactual Reasoning
Simulate alternative realities. The logic of "what if" and decision evaluation.
Type Signature
Counterfactual : Actual → Intervention → Alternative → Comparison
Where:
Actual : Decision × Outcome → ActualWorld
Intervention : ActualWorld × Δ → ModifiedPremise
Alternative : ModifiedPremise → ProjectedOutcome
Comparison : (ActualWorld, ProjectedOutcome) → DifferenceAnalysis
When to Use
Use counterfactual when:
- Evaluating past decisions ("Should we have...")
- Scenario planning ("What if X happens...")
- Comparing options not taken ("If we had chosen...")
- Strategic simulation ("If competitor does X...")
- Learning from outcomes ("Was our decision right?")
Don't use when:
- Executing known process → Use Causal
- Explaining observation → Use Abductive
- Resolving disagreement → Use Dialectical
Core Principles
Minimal Intervention
Change only what's necessary to test the hypothesis:
- Modify one variable at a time where possible
- Keep everything else constant (ceteris paribus)
- Trace downstream effects carefully
Probability Weighting
Alternative outcomes aren't certain:
- Assign probability to each projected outcome
- Consider multiple possible alternatives per intervention
- Avoid overconfidence in projections
Asymmetry Awareness
Counterfactual analysis has inherent biases:
- Hindsight makes alternatives seem clearer
- Survivors don't see paths that led to failure
- Confidence in projections often too high
Four-Stage Process
Stage 1: Actual World
Purpose: Document the decision made and observed outcome.
Components:
actual:
decision:
what: "The choice that was made"
when: ISO8601
who: "Decision maker(s)"
context: "Circumstances at decision time"
alternatives_considered: [string] # At the time
outcome:
result: "What actually happened"
metrics:
- metric: "Measurable outcome"
value: number
expected: number # What was predicted
timeline: "How long to outcome"
assessment:
success_level: high | medium | low | failed
surprise_level: 0.0-1.0 # How unexpected
causal_chain:
- step: "Decision led to X"
- step: "X led to Y"
- step: "Y produced outcome"
Example:
actual:
decision:
what: "Priced enterprise tier at $50K/year"
when: "2024-06-01"
who: "Founders"
context: "First enterprise launch, no market data"
alternatives_considered:
- "$30K/year (lower barrier)"
- "$75K/year (higher margin)"
- "Usage-based pricing"
outcome:
result: "Closed 3 deals in 6 months, $150K ARR"
metrics:
- metric: "Deals closed"
value: 3
expected: 5
- metric: "ARR"
value: 150000
expected: 250000
- metric: "Sales cycle"
value: 120 # days
expected: 90
timeline: "6 months"
assessment:
success_level: medium
surprise_level: 0.4 # Somewhat below expectations
causal_chain:
- step: "$50K price point set"
- step: "3/5 prospects required CFO approval at this level"
- step: "CFO approval added 30 days to cycle"
- step: "2 deals lost to budget cycle timing"
Stage 2: Intervention
Purpose: Define the alternative decision to evaluate.
Intervention Types:
| Type | Description | Example |
|---|---|---|
| Price | Different pricing decision | "$30K instead of $50K" |
| Timing | Earlier or later action | "Launched 3 months earlier" |
| Strategy | Different strategic choice | "SMB-first instead of enterprise" |
| Resource | Different allocation | "Hired sales earlier" |
| Partner | Different relationship | "Partnered with X instead of Y" |
Components:
intervention:
what: "The alternative choice"
change:
variable: "What's being changed"
from: "Actual value"
to: "Alternative value"
rationale:
why_consider: "Why this alternative is worth evaluating"
was_available: bool # Was this actually an option at the time?
assumptions:
held_constant:
- "What we assume stays the same"
ripple_effects:
- "Expected downstream changes"
Example:
intervention:
what: "Price at $30K/year instead of $50K"
change:
variable: "Enterprise tier annual price"
from: "$50,000"
to: "$30,000"
rationale:
why_consider: "Test if lower price would have increased velocity"
was_available: true # This was considered at the time
assumptions:
held_constant:
- "Same product features"
- "Same sales team"
- "Same market conditions"
- "Same target customer profile"
ripple_effects:
- "Different approval threshold (manager vs CFO)"
- "Potentially different customer expectations"
- "Lower margin per deal"
Stage 3: Alternative Projection
Purpose: Project what would have happened under the intervention.
Projection Method:
- Identify decision point - Where paths diverge
- Trace causal chain - What changes downstream?
- Estimate outcomes - With probability weights
- Consider multiple scenarios - Best/worst/expected
Components:
alternative:
scenarios:
- name: "Expected case"
probability: 0.6
outcome:
deals: 6 # vs actual 3
arr: 180000 # vs actual 150000
cycle: 75 # days, vs actual 120
reasoning: "Lower price = faster approval, more deals, but lower $ each"
- name: "Optimistic case"
probability: 0.25
outcome:
deals: 8
arr: 240000
cycle: 60
reasoning: "Volume effect stronger than expected"
- name: "Pessimistic case"
probability: 0.15
outcome:
deals: 4
arr: 120000
cycle: 90
reasoning: "Lower price signals lower value, some prospects hesitate"
weighted_outcome:
deals: 6.0 # (6×0.6 + 8×0.25 + 4×0.15)
arr: 178000
cycle: 74
causal_reasoning:
- "At $30K, most prospects can approve at director level"
- "Director approval takes ~45 days vs CFO 90+ days"
- "Faster cycle = more deals in same period"
- "But: lower price per deal = lower total ARR per deal"
confidence: 0.65 # How confident in this projection
key_uncertainties:
- "Would lower price attract different (worse?) customers?"
- "Would sales team close at same rate at lower price?"
- "Would competitors have responded differently?"
Stage 4: Comparison
Purpose: Compare actual vs alternative, extract insights.
Components:
comparison:
quantitative:
- metric: "Deals"
actual: 3
alternative: 6.0
difference: "+3 (100%)"
direction: better
- metric: "ARR"
actual: 150000
alternative: 178000
difference: "+$28K (19%)"
direction: better
- metric: "Sales cycle"
actual: 120
alternative: 74
difference: "-46 days (38%)"
direction: better
- metric: "ARR per deal"
actual: 50000
alternative: 29667
difference: "-$20K (41%)"
direction: worse
qualitative:
better_in_alternative:
- "Faster sales velocity"
- "Lower customer acquisition cost"
- "More reference customers faster"
worse_in_alternative:
- "Lower margin per customer"
- "Potentially lower perceived value"
- "Less room for discounting"
verdict:
assessment: "Alternative likely better overall"
confidence: 0.65
caveat: "Lower price creates different customer dynamics long-term"
insight:
learning: "At this stage, velocity matters more than margin"
applies_to: "Early enterprise sales with unproven product"
recommendation: "Consider price reduction or tier restructuring"
action_implication:
retrospective: "Pricing decision was suboptimal but not catastrophic"
prospective: "For next segment, start lower and raise after validation"
Quality Gates
| Gate | Requirement | Failure Action |
|---|---|---|
| Actual documented | Outcome with metrics | Gather actual data |
| Intervention minimal | Single variable change | Simplify intervention |
| Scenarios weighted | Probabilities sum to 1.0 | Adjust probabilities |
| Confidence bounded | State uncertainty explicitly | Add confidence intervals |
| Insight actionable | Clear learning for future | Extract practical lesson |
Intervention Validity
Not all counterfactuals are useful:
Valid interventions:
- Was actually an option at the time
- Changes something controllable
- Has traceable downstream effects
- Provides actionable insight
Invalid interventions:
- "What if we had known X" (not available info)
- "What if competitor hadn't existed" (not controllable)
- "What if market was bigger" (not a decision)
Common Failure Modes
| Failure | Symptom | Fix |
|---|---|---|
| Hindsight bias | Alternative seems obviously better | Account for what was knowable at decision time |
| Single scenario | Only one alternative considered | Generate multiple scenarios with probabilities |
| Overconfidence | High certainty in projections | Widen confidence intervals |
| Untraceable | Can't explain why alternative differs | Build explicit causal chain |
| Fantasy | Intervention wasn't actually available | Verify intervention was feasible |
Multiple Interventions
For complex decisions, evaluate multiple alternatives:
interventions:
- name: "Lower price ($30K)"
outcome: {arr: 178000, deals: 6}
- name: "Higher price ($75K)"
outcome: {arr: 150000, deals: 2}
- name: "Usage-based pricing"
outcome: {arr: 200000, deals: 4}
confidence: 0.5 # Higher uncertainty
comparison_matrix:
best_arr: "Usage-based"
best_velocity: "Lower price"
best_margin: "Higher price"
best_overall: "Lower price (velocity matters most at this stage)"
Output Contract
counterfactual_output:
actual:
decision: string
outcome: {result: string, metrics: [Metric]}
success_level: string
intervention:
what: string
change: {variable: string, from: any, to: any}
was_available: bool
alternative:
scenarios: [Scenario]
weighted_outcome: {metric: value}
confidence: float
comparison:
quantitative: [{metric: string, actual: any, alternative: any, direction: string}]
verdict: string
confidence: float
insight:
learning: string
applies_to: string
recommendation: string
action:
retrospective: string # What does this mean for past decision
prospective: string # What does this mean for future decisions
next:
suggested_mode: ReasoningMode # Usually causal
canvas_updates: [string]
experiments_to_run: [string]
trace:
interventions_evaluated: int
confidence_average: float
duration_ms: int
Example Execution
Context: "Should we have taken the Series A when offered 18 months ago?"
Stage 1 - Actual:
Decision: Declined $5M Series A at $20M valuation
Outcome: Bootstrapped to $600K ARR, now raising at $30M valuation
Success level: Medium-high (slower growth, higher ownership)
Stage 2 - Intervention:
What: Accepted $5M Series A
Change: Funding status from bootstrapped to funded
Was available: Yes, term sheet was on the table
Stage 3 - Alternative:
Scenarios:
- Expected (60%): $1.5M ARR now, but 25% dilution
- Optimistic (25%): $2M ARR, enterprise sales team
- Pessimistic (15%): $800K ARR, burned capital on wrong bets
Weighted: $1.4M ARR, 75% ownership vs current $600K ARR, 100% ownership
Stage 4 - Comparison:
ARR: Alternative 133% higher
Ownership value: Alternative $31.5M (75% × $42M) vs Actual $30M (100% × $30M)
Net: Roughly equivalent in value, different risk profiles
Verdict: Decision was reasonable given risk tolerance
Insight: Bootstrapping is viable if willing to accept slower growth
Recommendation: Current path validated, continue unless growth accelerates