/strategy-stakes-review

name: strategy-stakes-review
description: "Use when you want a strategic-fit and opportunity-cost check on a text artifact before it ships — assess goal alignment against the operator's life-goals or portfolio framework, name the specific opportunity cost (what queued work this preempts), run the kill-criteria check, and assess identity coherence with the operator's executive arc. Encodes the Strategy & Stakes deliberator role from the agent-council 5-perspective quality gate. Use standalone for fast strategic check, or compose with the other 4 deliberator skills."
version: "0.1.1"
type: "codex"
tags: ["Quality Gate", "Strategy", "Portfolio", "Council Deliberator"]
created: "2026-05-29"
valid_until: "2026-11-29"
derived_from: "prompts/strategy.md in Avyayalaya/agent-council"
tested_with: ["Claude Sonnet 4.6", "Claude Opus 4.6", "GPT-4o"]
license: "MIT"
composes_with:
  - package: "agent-council"
    skill: "skeptic-review"
    relation: "use_together"
    reason: "When Skeptic surfaces an unaddressed counter-position that has strategic consequences ('smart competitor reads this and rebuts in one tweet'), Strategy & Stakes integrates that into the identity-coherence and strategic-risk assessment."
  - package: "agent-council"
    skill: "adjudicator-synthesis"
    relation: "produces_input_for"
    reason: "Strategy's goal-fit + opportunity-cost + kill-criteria structured output feeds into the Adjudicator's verdict policy and reasoning."
  - package: "pm-skills"
    skill: "product-strategy"
    relation: "use_after"
    reason: "Strategy & Stakes audits whether an artifact's positioning is consistent with a previously articulated product strategy. Run after producing strategy via pm-skills' product-strategy skill."
  - package: "pm-skills"
    skill: "go-to-market-strategy"
    relation: "use_after"
    reason: "GTM artifacts benefit from a strategic-fit gate — does the campaign align with the chosen GTM motion, or does it leak into a different positioning?"
  - package: "pm-skills"
    skill: "stakeholder-alignment"
    relation: "use_with"
    reason: "Strategy & Stakes flags identity-coherence risk; stakeholder-alignment helps plan how the strategic message lands with specific stakeholders."
capability_summary: "Produces a structured Strategy & Stakes critique of a text artifact: primary and secondary goal alignment with fit assessment, named opportunity cost (specific queued alternative the artifact preempts), kill-criteria check (triggered + criterion + reason), identity-coherence one-liner, the one strategic risk worth naming, would_block + irreducible flags. Output is fenced JSON suitable for downstream verdict aggregation."
input_schema:
  artifact: "string or path — the text artifact to assess strategically"
  goals_framework: "object or path — required, canonical goals (e.g., a goals.md with named goal tracks, an OKR set, or a strategy hierarchy)"
  proof_stack: "object or path — optional, where evidence gaps are by goal dimension"
  dispatch_queue: "object or path — optional, what other work is queued and competing for the same hour"
  kill_criteria: "object or path — optional, committed kill-conditions per project (often in registry.json or strategy doc)"
  prior_round_critiques: "object — optional, all 4 R1 critiques from other deliberators when running Round 2 cross-read rebuttal"
output_schema:
  role: "Constant: strategy"
  round: "1 (independent critique) or 2 (cross-read rebuttal)"
  score: "1-5 where 1 = goal-misaligned + identity-incoherent + high opportunity cost, 5 = perfectly aligned + low opportunity cost"
  goal_alignment: "Object {primary_goal, secondary_goal, fit: Strong|Adequate|Weak}"
  opportunity_cost: "Specific sentence naming the queued work the artifact preempts"
  kill_check: "Object {triggered: boolean, criterion: string or null, reason: string or null}"
  identity_coherence: "One sentence on whether the public face matches the operator's executive arc"
  strategic_risk: "The one risk worth surfacing, ≤1 sentence"
  would_block: "Boolean — true if misaligned, high opportunity cost with weaker compounding, or kill-criterion triggered"
  irreducible: "Boolean — true only if strategic mismatch requires routing to different channel or shelving"
  notes: "≤2 sentences on overall strategic posture"
example_invocation: "examples/demo/sample_linkedin_post.md"

Purpose

Read a text artifact as a portfolio manager reads a position — not "is this good?" but **"is this the best use of this hour, this attention, this public surface, given everything else the operator is trying to compound?"**

The artifact arrives optimized for itself. It survived the operator's own gate. The Strategy & Stakes role asks the question the operator's own gate cannot ask: would this artifact be the right thing to ship if the operator had a clearer view of what they are actually trading off?

The role is not a brake. It is a portfolio overlay. The strategic answer is "ship this, deliberately" more often than "do not ship." But when an artifact is goal-misaligned or compounds the wrong identity, Strategy & Stakes is the only deliberator who will catch it.

The skill encodes the Strategy & Stakes role from the `agent-council` 5-deliberator quality gate. Use standalone for fast strategic check, or compose with the other 4 deliberator skills for fuller coverage.

When to Use / When NOT to Use

**Use this skill when:**

• You have a draft Tier-1 artifact and want to confirm it serves the highest-leverage goal before spending the publish hour on it
• You suspect opportunity cost is high (some queued work would compound more than this artifact) and want it named
• You want to surface identity-coherence risk — does this artifact match the operator's executive arc, or does it drift into a positioning the operator does not actually hold?
• Kill-criteria are committed for the project (in `registry.json` or a strategy doc) and you want them checked before publish
• You are running a mu