mark-kashef-wargame-os

name	Mark Kashef Wargame OS
description	Fire when a mission will be executed by a cheaper model/session than the one planning it, when a wrong turn mid-execution is expensive, or when Farrice says wargame/battle plan/pre-fight/judgment banking. Converts frontier-model judgment into a failure-map a cheap executor runs blind.
version	1.0
expert	mark-kashef
domain	wargame, wargaming, battle plan, pre-execution simulation, failure map, plan vs wargame, executor brief, judgment banking, cheaper model execution, RECON NEEDED, abort conditions, expected observation, red-team the plan, blind executor, mission brief, breadth-first drafting, /goal contract, refinement loop, tier degrade, model handoff
when_to_use	["A deliverable/build will be executed by Sonnet/a cheaper tier and the route needs frontier judgment banked first","High-stakes mission where improvising mid-run is costlier than simulating first (client work, launches, migrations)","A plan keeps dying at 80% and the last 20% lands back on the expensive model","Batch of meaty projects to draft breadth-first before any gets polished","A handoff document must be executable blind — zero questions from the receiving session"]
workflows	10
routing	core-candidate

Mark Kashef — Wargame OS

Pre-execution adversarial simulation. Not a plan: a plan assumes linearity and a blue-sky scenario; a wargame fights the mission on paper — every move with its expected observation, its likely failure + the cause it signals + the counter-move, every fork with a trigger, RECON NEEDED marks with exact settling checks, abort conditions, and verification runs — written so a cheaper model executes it blind, "without asking a single question."

The economics: "You pay for the genius once. You keep it forever." Judgment is expensive to generate, nearly free to replay. This skill is the artifact form of "Fable orchestrates, Sonnet executes" and the mechanism that makes the tier-degrade policy safe.

Recognition test: would Kashef see a route fought on paper — or a plan wearing a costume? "Wargamed means it survives contact." If you can't name the attack it survived, it isn't wargamed.

Workflows

Tier 1 — Foundation

Workflow	Produces	Use when
wargame-order	A complete wargame order (WARGAME ORDER preamble + executor mission brief) in a scaffolded mission folder	Front door — any single mission entering the system
wargame-run	The fought-on-paper wargame file (mission spec → RECON NEEDED → Moves/Expect/Fail/Trigger → aborts → verification)	An order exists; bank the judgment at highest tier/effort
wargame-grade	Point-by-point 8-point grade + recorded red-team attack + patch + DONE/NOT-DONE/BLOCKED verdict in the ledger	Every draft, before ANY executor touches it
wargame-execute	Execution by a cheaper model following the route blind + expected-vs-observed ledger entry	Wargame is DONE; time to spend cheap tokens

Tier 2 — Practitioner

Workflow	Produces	Use when
wargame-batch	All missions drafted breadth-first via the /goal contract + /loop refinement to DONE/BLOCKED	A laundry list of missions, not one
wargame-recon	Recon dossier — unknown-knowns elicited, unknown-unknowns enumerated, frozen-choice list	Before wargame-order on anything ambiguous ("the wargame drags the other three boxes into the light")