brieflisted

# /operator-cmo:brief This is the gate between "someone asked for a thing" and "the machine starts producing". It exists because the failure mode of an agent marketing stack is not bad writing. It is excellent writing about nothing anyone decided to say. ## The decision guard Run this before anything else, every time. 1. Read `marketing/decisions/positioning.md`. Missing? Stop. Tell the operator to run `/operator-cmo:positioning`. 2. Read `marketing/decisions/quarter.md`. Missing? Stop. Tell the operator to run `/operator-cmo:quarter`. 3. Check the `ends:` date in quarter.md. Past it? Stop. The plan expired, and producing against an expired plan is how a stack keeps executing a strategy that was abandoned in a meeting nobody wrote down. Never invent, infer or "assume for now" a missing decision file. Stopping is the feature. ## The refusal Map the request to exactly one bet id from quarter.md. If it maps to none, do not write the brief. Write `marketing/briefs/YYYY-MM-DD-<slug>.no-bet.md` containing the request, the bets it was tested against, and why none of them fit. Then give the operator three options, in this order: 1. Drop it. 2. Add it to `Not doing this quarter` in quarter.md. 3. Change the quarter plan, which means killing or shrinking an existing bet to pay for it. Present option 3 last and name what it costs. Most requests die honestly at option 1 once the price of option 3 is visible. ## The brief When it does map, write `marketing/brief