Update to Marketing Compass

{
  "description": "Design marketing communications from a defined customer-state transition, meaning, recall, trust, comparison, expectation, and action path rather than from channels. Use when a user asks for a communications strategy, brand message, awareness or recall plan, PESO or touchpoint roles, TV/PR/SNS/Web/store integration, a functional-versus-emotional message decision, expectation and UX alignment, word-of-mouth or buzz design, or a route from paid contact into owned assets, search, sales, store, product, or customer success.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 491
    },
    {
      "relative_path": "assets/icon.svg",
      "size_in_bytes": 509
    },
    {
      "relative_path": "references/output-contract.md",
      "size_in_bytes": 2716
    },
    {
      "relative_path": "references/state-and-meaning.md",
      "size_in_bytes": 2867
    },
    {
      "relative_path": "references/touchpoint-and-transmission.md",
      "size_in_bytes": 2453
    }
  ],
  "name": "design-marketing-communications",
  "skill_md_contents": "---\nname: design-marketing-communications\ndescription: \"Design marketing communications from a defined customer-state transition, meaning, recall, trust, comparison, expectation, and action path rather than from channels. Use when a user asks for a communications strategy, brand message, awareness or recall plan, PESO or touchpoint roles, TV/PR/SNS/Web/store integration, a functional-versus-emotional message decision, expectation and UX alignment, word-of-mouth or buzz design, or a route from paid contact into owned assets, search, sales, store, product, or customer success.\"\n---\n\n# Design Marketing Communications\n\nDesign the customer-state transition before selecting media or producing messages. Communication is one intervention within marketing; do not use it to replace product value, availability, price, implementation, or experience.\n\nRead [references/state-and-meaning.md](references/state-and-meaning.md) for every substantive design. Read [references/touchpoint-and-transmission.md](references/touchpoint-and-transmission.md) when assigning PESO, real/digital roles, or word-of-mouth. Read [references/output-contract.md](references/output-contract.md) before returning a complete strategy.\n\n## Establish the decision\n\nIdentify:\n\n- Who must decide what and by when\n- The customer, buying situation, and demand state\n- The current customer state\n- The single next state communication should create\n- The behavior or downstream path that state should enable\n- Product, price, distribution, experience, sales, or operational constraints\n- The acceptable cost, trust risk, and review horizon\n\nIf the primary bottleneck is product value, availability, adoption, or continuation, do not recommend communication as the primary solution. Ask at most three questions that can change the state transition, then proceed provisionally when possible.\n\n## Define one state transition\n\nUse the smallest relevant path:\n\n```text\nLatent or unrecognized need\n  → recognition or category entry\n  → awareness and memory\n  → recall in the buying situation\n  → understanding and meaning\n  → trust, preference, or consideration\n  → comparison and choice\n  → intended action\n  → expectation and experience\n  → re-recall, re-selection, or advocacy\n```\n\nName:\n\n- Current state\n- Desired next state\n- Barrier to transition\n- Customer evidence that the transition occurred\n- Downstream owner after communication\n\nDo not attempt to move every state in one execution. Recall and trust may support multiple stages, but still define the primary transition.\n\n## Diagnose the buying condition\n\nClassify only what changes the design:\n\n- Convenience versus specialty purchase\n- Low versus high involvement\n- Impulse versus planned purchase\n- Individual versus organizational decision\n- Immediate demand versus future demand\n- Search-led, shelf-led, relationship-led, or habit-led choice\n\nTreat these as contextual dimensions, not fixed product categories. The same offer may require different communication by use case.\n\n## Design the meaning\n\nUse:\n\n```text\nProduct → meaning → customer context → choice\n```\n\nDefine:\n\n- The customer as subject, not the brand\n- The situation in which the message should be recalled\n- One meaning the customer should reconstruct\n- The choice reason that meaning supports\n- Proof or experience that makes it credible\n- What should not be remembered or overpromised\n\nMeasure success by what was reconstructed, not what was transmitted. Reduce information before adding more. Do not use brand jargon that requires the sender to explain it.\n\n## Balance function, story, emotion, and logic\n\nAssign roles rather than choosing a universal winner:\n\n- Function creates understanding and practical credibility.\n- Story creates context, empathy, and motivation.\n- Emotion starts or accelerates attention and action.\n- Logic removes uncertainty, perceived risk, and braking forces.\n\nMatch the mix to involvement, decision risk, prior knowledge, and channel context. Do not frame function versus story or emotion versus reason as a permanent binary.\n\n## Design recall and selection\n\nFor recall work, specify:\n\n- Category-entry or need moment\n- Memory cue\n- Distinctive meaning or association\n- Reach and repetition logic\n- Competitive and physical availability context\n- Route from recall to access or comparison\n\nDo not equate delivered awareness with recall in a buying situation. If the offer is recalled but not chosen, work on selection reason, proof, price, risk, or access rather than more awareness alone.\n\n## Align expectation and experience\n\nMap the promise across advertising, PR, social proof, site, sales, store, packaging, onboarding, product, and CS.\n\nCheck:\n\n- What expectation communication creates\n- What the customer actually experiences\n- Time and effort to reach value\n- Where overstatement creates disappointment\n- Where under-explaining prevents value recognition\n- Which downstream team owns the handoff\n\nDo not maximize conversion by creating expectations the experience cannot satisfy.\n\n## Assign touchpoint roles\n\nUse PESO as a role map, not a checklist:\n\n- **Paid:** controlled contact, reach, timing, and short-term acceleration.\n- **Earned:** third-party credibility, public relevance, and interpretation.\n- **Shared:** peer transmission, participation, conversation, and UGC.\n- **Owned:** depth, evidence, comparison, action, relationship, and reusable memory.\n\nAssign every touchpoint one primary state transition and a handoff. Connect paid contact to owned or operational assets when continued understanding, action, or relationship matters.\n\nCombine digital breadth and observability with analog depth, embodiment, proximity, or trust where useful. Do not default to either channel family.\n\n## Design transmission without promising buzz\n\nFor word-of-mouth or buzz, design:\n\n- The reason one person would give it to another\n- The narrow first subject who sees themselves in it\n- The existing conversation, frustration, identity, or useful task it joins\n- The emotion the sharing helps process\n- The social cost or ambiguity that might stop transmission\n- A path for meaning to remain accurate as it travels\n\nTreat content, timing, platform, context, and emotion as an interacting chain. Do not promise virality, reach, who will be hit, or repeatability.\n\n## Define measurement and guardrails\n\nSelect measures that match the transition:\n\n- Delivery: reach, exposure, frequency, completion\n- State change: recognition, recall, understanding, trust, preference, consideration\n- Path behavior: search, direct visit, comparison, store action, inquiry, trial\n- Experience: expectation gap, activation, satisfaction, complaint, return, continuation\n- Transmission: share motive, message fidelity, relevant conversation, earned response\n\nUse:\n\n```text\nBaseline\nDesired Signal\nCounter-signal\nGuardrail\nReview window\nAction if crossed\n```\n\nDo not attribute sales directly without a defensible counterfactual and control of material non-communication variables.\n\n## Return a communications design\n\nUse the compact or full structure in [references/output-contract.md](references/output-contract.md). Include:\n\n- Current and desired customer state\n- Barrier and intervention mechanism\n- Meaning to reconstruct and proof\n- Function/story/emotion/logic roles\n- PESO and touchpoint handoffs\n- Expectation-experience alignment\n- Signal, counter-signal, guardrail, and review point\n- What not to communicate or optimize\n\n## Guardrails\n\n- Do not select channels before defining the state transition.\n- Do not use communication to cover absent product value or availability.\n- Do not call exposure, impressions, or views customer-state change.\n- Do not optimize immediate conversion through false scarcity, misleading framing, or expectation inflation.\n- Do not equate awareness with recall, preference, or choice.\n- Do not present function and story, emotion and logic, or digital and analog as fixed opposites.\n- Do not promise buzz, earned coverage, UGC, or precise virality.\n- Do not attribute revenue to communication without a defensible counterfactual.\n- Do not present Marketing Compass classifications as universal industry terminology.\n"
}