contentlisted

# /operator-cmo:content Writing is the easy half. The half that decides whether this stack is worth running is what you refuse to write. ## The decision guard 1. Read the brief. If the operator did not name one, list the briefs in `marketing/briefs/` from the last 14 days and ask which. If there is no brief, stop and run `/operator-cmo:brief` first. Do not write from a prompt. 2. Read `marketing/decisions/positioning.md` for the proof you are allowed to use, and `marketing/policy/voice.md` for how it should sound. If the voice file is missing or still the empty template, say so once and offer `templates/voice-operator-preset.md`, which is a real filled-in voice with the AI-slop bans already in place. Writing to a blank voice file produces competent generic copy, which is the most expensive kind. 3. Read the brief's `bet:` and `gate:` fields. They go in the output header. ## Write Follow the brief's one belief. Everything in the asset either supports it or comes out. Structure by default: open on the specific problem or a number, put the mechanism in the middle, end on what the reader should do or decide. No throat-clearing, no summary of what you just said. ## The claim pass Before the draft is saved, check every factual statement: - Traceable to a proof line in positioning.md? Keep it. - Not traceable? Either cut it or mark it inline as `[unverified]` and list it at the end of the file under `## Claims needing evidence`. - A number, a customer