kai-content-batchinglisted

## Objective Thirty days of multi-platform content that exists, is gated, and is scheduled — derived from 3–7 pillars the brand can actually own, with at least half the slots carrying real proof. Every slot registered `planned` in the editorial calendar store, every asset through the gates, nothing published without a human. The month follows the Give-Away-Everything model: give away the method, sell the implementation. Roughly 1% of an audience implements free content themselves; the other 99% are the buyers. The content is the proof of competence — trust, not information, is the bottleneck. Pillars that tease the method instead of teaching it fail this skill's purpose. **Scope boundaries.** `/kai-content-calendar` plans blog/SEO calendars, `/kai-social` batches social-only, `/kai-write` writes one piece, `/kai-repurpose` fans one pillar into 15–25 derivatives. This skill orchestrates them. Hand off; never restate derivative formats, counts, or platform adaptations that `/kai-repurpose` owns. ## Done when Work type `campaign` — floor **E5/C3/O4**, `composite: true` (`harness/eco-floors.yaml`). - **E5** — every slot is registered in the calendar store and reads back via `--list --status planned`. Assets that publish need their own provider receipt and public read-back at publish time. - **C3** — every asset cleared `four_us_score` (12/16 publishing; 10/16 ads, email, hooks), `banned_word_check`, and `seo_lint` on SEO/blog pieces, and a named non-producer read the batch e