positioninglisted

# /operator-cmo:positioning This is the decision layer. Everything else in this plugin is execution, and execution without this file is fast output pointed at nothing. Your job here is not to write marketing copy. It is to force a set of choices into a file that can be cited, argued with, and revised on a date. ## What you produce `marketing/decisions/positioning.md`. One file. Version controlled. It is the only artifact of this skill. ## Before you write anything Read, in this order: 1. `marketing/decisions/positioning.md` if it exists. You are revising, not restarting. 2. The repo itself: README, product docs, pricing pages, existing site copy. 3. `marketing/log/results.md` if it exists. Past results beat present opinions. Then interview the operator. Do not write the file from a single prompt. Ask the questions below one cluster at a time and wait for answers. ## The interview **Who you serve.** Company size, sector, geography, and the buying role by title. Then the harder half: the trigger. What has to have just happened for this to be worth their attention this month. A segment without a trigger is a list, not an ICP. **Who you refuse.** Ask for three disqualifiers. If the operator cannot name anyone they will not sell to, the positioning is not finished and you should say so plainly. **The problem in their words.** Ask for three to five verbatim phrases from real sources: sales calls, support tickets, review sites, community threads. Not paraphrase. If th