diff --git a/plan-ceo-review/SKILL.md b/plan-ceo-review/SKILL.md
index 57cbf5464..7c6006123 100644
--- a/plan-ceo-review/SKILL.md
+++ b/plan-ceo-review/SKILL.md
@@ -809,6 +809,12 @@ branch name wherever the instructions say "the base branch" or `<default>`.
 
 # Mega Plan Review Mode
 
+> **Execution settings recommendation**
+> Bounded strategic review: assess a plan against business / product /
+> investor framing. Second-tier compute (e.g., Opus Extra high) is
+> right. Top-tier compute is warranted only when the plan involves
+> material strategic ambiguity that benefits from open-ended exploration.
+
 ## Philosophy
 You are not here to rubber-stamp this plan. You are here to make it extraordinary, catch every landmine before it explodes, and ensure that when this ships, it ships at the highest possible standard.
 But your posture depends on what the user needs:
diff --git a/plan-ceo-review/SKILL.md.tmpl b/plan-ceo-review/SKILL.md.tmpl
index cd51ece29..73e8df714 100644
--- a/plan-ceo-review/SKILL.md.tmpl
+++ b/plan-ceo-review/SKILL.md.tmpl
@@ -57,6 +57,12 @@ gbrain:
 
 # Mega Plan Review Mode
 
+> **Execution settings recommendation**
+> Bounded strategic review: assess a plan against business / product /
+> investor framing. Second-tier compute (e.g., Opus Extra high) is
+> right. Top-tier compute is warranted only when the plan involves
+> material strategic ambiguity that benefits from open-ended exploration.
+
 ## Philosophy
 You are not here to rubber-stamp this plan. You are here to make it extraordinary, catch every landmine before it explodes, and ensure that when this ships, it ships at the highest possible standard.
 But your posture depends on what the user needs:
diff --git a/plan-eng-review/SKILL.md b/plan-eng-review/SKILL.md
index c4ec10bb6..39fc15147 100644
--- a/plan-eng-review/SKILL.md
+++ b/plan-eng-review/SKILL.md
@@ -748,6 +748,13 @@ Skills that run plan reviews (`/plan-*-review`, `/codex review`) include the EXI
 
 # Plan Review Mode
 
+> **Execution settings recommendation**
+> Bounded engineering planning: produce a build plan from a spec, with
+> known target files and patterns. Second-tier compute (e.g., Opus
+> Extra high) handles this cleanly. Top-tier compute is warranted only
+> if the spec is unusually large or touches an unfamiliar codebase
+> region.
+
 Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction.
 
 ## Priority hierarchy
diff --git a/plan-eng-review/SKILL.md.tmpl b/plan-eng-review/SKILL.md.tmpl
index 09f5b163a..f1ebd12f3 100644
--- a/plan-eng-review/SKILL.md.tmpl
+++ b/plan-eng-review/SKILL.md.tmpl
@@ -35,6 +35,13 @@ triggers:
 
 # Plan Review Mode
 
+> **Execution settings recommendation**
+> Bounded engineering planning: produce a build plan from a spec, with
+> known target files and patterns. Second-tier compute (e.g., Opus
+> Extra high) handles this cleanly. Top-tier compute is warranted only
+> if the spec is unusually large or touches an unfamiliar codebase
+> region.
+
 Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction.
 
 ## Priority hierarchy