kai-launchlisted

# /kai-launch — One Launch, One Message, Every Channel > **Kai root note:** `knowledge/`, `harness/`, and `scripts/` paths in this skill live in the Kai install, not the user's project. Resolve them against the first ancestor directory of this SKILL.md that contains a `knowledge/` folder (the Kai plugin root, `~/.claude/kai`, or the kai-cmo-harness repo). `MARKETING.md`, `memory/`, and any output files live in the current project. If a referenced `scripts/` command is not available in this install, say so, skip it, and continue with the file-based guidance — never fabricate its output. ## Objective A dated launch a team can execute: a phased timeline, an asset set scoped to the channels the business actually has, and every asset carrying the same value proposition, the same proof points, and the same CTA destination. Plus a post-launch monitoring plan that says what to watch, when, and what to do when a number goes the wrong way. The failure mode this skill exists to prevent is a launch where the ad, the email, and the page each describe a slightly different product. ## Done when Work type `campaign` — floor **E5/C3/O4** (`harness/eco-floors.yaml`, contract `harness/skill-contracts/campaign.yaml`). Composite: the launch is CLOSED only when every child asset is CLOSED and the campaign-level threshold is met. One unshipped asset keeps the launch open. - **E5** — each asset reaches its own execution target and someone other than its producer reads it back at the live targ