reviewlisted

# /operator-cmo:review Everything else in this plugin reads the decision files. This is the only skill that writes to them, and only after showing the operator a diff. A stack that produces but never revises its own plan is not a marketing system. It is a content mill with good manners. ## Inputs 1. `marketing/decisions/quarter.md`: the bets, their metrics, their kill dates. 2. `marketing/log/results.md`: what actually happened. If it is empty or stale, say so first and ask for the numbers. Do not estimate them, and do not read activity counts as outcomes. 3. `marketing/drafts/` and `marketing/log/shipped.md`: what was produced and what went out. The gap between the two is the review bottleneck, measured. ## The weekly pass For each bet: metric, baseline, current, target, days left, and one of three verdicts. - **On track.** Nothing to change. Say it in one line and move on. - **Off track, keep.** Name the specific thing that will be different next week. "Try harder" is not a thing. - **Kill.** The kill condition fired. Say so plainly, name where the budget and hours move, and write the diff to quarter.md. Do not soften a fired kill condition, and do not extend the date because the bet is nearly there. The date was the decision. Then three numbers that describe the machine rather than the market: - **Produced vs shipped.** If produced is much larger than shipped, the gate is the constraint and you should throttle production, not add more skills. -