check-before-i-publishlisted

# check-before-i-publish ## Context load Run `rainmaker context --check` first. It prints what exists, what is stale, and exits 1 if anything this skill requires is missing. Then read, in this order: 1. `context/business.md` in full. If absent, stop: "No business context. Run `rainmaker audit`, then the `know-my-buyer` skill." 2. `context/voice.md` if this skill writes prose. If absent, stop and say so. 3. `context/glossary.md` if this skill names products, features or competitors. 4. `data/strategy.json` if this skill reads or writes strategy. 5. Only the `data/` files listed in this skill's Consumes table. Never crawl or call an API the core already covers. If `strategy.json.context_hash` does not match the current hash of `context/business.md`, say exactly: "Business context was edited after the strategy was written. Re-run `know-my-buyer`, or run `rainmaker context --sync` to accept the prose as authoritative." Then stop. If `context/business.md` carries `confidence: stub`, continue, and stamp every output with: "Built on a stub context. Nothing in it came from a buyer. Run `know-my-buyer` to replace it." ## Consumes | File | Why | If missing | |---|---|---| | the brief and draft | preflight input | ask for the slug | | `data/ledger.jsonl` | shipped timestamps, for postflight windows | run `rainmaker ledger --rebuild` | | `data/snapshots/<latest>/*` | current measured values for postflight gates | run `rainmaker audit` | ## Produces Nothing persisted; a pass/f