ship-betlisted

# ship-bet (skeleton) This is a reusable operating recipe, not a one-off run file. Use it when the operator wants to turn one proposed bet or offer into a launch push with a landing page, first ad creative, review evidence, and a saved checkpoint. **Current status: skeleton.** This file documents the intended chain and artifact routing. It is not yet executable as one coherent workflow with a single progress surface, retry-on-failure, or cross-skill data passing. Run each step through the named skills and `mb` commands today. ## Playbook Versus Run This file is the reusable engine recipe under `.claude/playbooks/ship-bet/`. The concrete run belongs in the business repo: ```text pushes/<YYYY-MM-DD-slug>/push.md pushes/<YYYY-MM-DD-slug>/playbooks/ship-bet.md ``` Create or select the push first. Use a push playbook run record when the run needs approval state, provider readiness, forks from the recipe, manual steps, review evidence, or outcome links. Do not write new work under `campaigns/`; that folder is legacy compatibility read only. ## Intended Flow ``` 1. /mb-start — read repo health, active bets, pushes, provider state 2. /mb-think codify — confirm bet, offer, audience, proof, and success bar 3. pushes/ — create or select the launch push record 4. skill-brief-draft — draft minisite brief from offer + audience + voice 5. skill-review — Seven Sweeps + Expert Panel against the brief 6. /mb-site build — generate or update the landing p