kai-brieflisted

# /kai-brief — A Brief `/kai-write` Can Execute Without Asking Anything ## Objective A structured content brief that fixes the strategy before drafting starts: format, keyword set, persona, the specific angle, three hook options, the audience pain, the proof on hand, the CTA, word count, and publish date. It is the handoff contract `/kai-write` and `/kai-email-system` consume. The angle is the load-bearing field — "AI for law firms" is a topic; "Why law firms lose 40% of leads after 5pm" is an angle. ## Done when Work type `strategy-plan` — floor **E3/C3/O1** (`harness/eco-floors.yaml`). - **E3** — the brief conforms to `harness/brief-schema.md` and the requester accepted it; `/kai-write` does not proceed on an unapproved brief. - **C3** — `banned_word_check` clean, and the three validation rules below hold under a read by someone other than the brief's author. - **O1** — the brief names the piece it spawns and its publish date. A brief nothing gets written from is not finished. ## Constraints - **Read `MARKETING.md` from the project root first.** It carries product, ICP, value prop, monetization, voice, current channels, and competitive landscape. If it does not exist, build it from the codebase — CLAUDE.md, README.md, PROJECT.md, package.json, landing pages, email/ad/analytics config — using the template from `/kai-email-system`, and confirm the draft. Do not ask the user what the product is. - **Six things must be known before the brief is written:** the format (blo