Update to PrePilot Lite

{
  "description": "Use when the user needs positioning, value proposition, message hierarchy, message house, category framing, audience-specific messaging, proof architecture, or a sharper reason to choose the product.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 257
    }
  ],
  "name": "positioning-messaging",
  "skill_md_contents": "---\nname: positioning-messaging\ndescription: Use when the user needs positioning, value proposition, message hierarchy, message house, category framing, audience-specific messaging, proof architecture, or a sharper reason to choose the product.\n---\n\n# Positioning and Messaging\n\n## Use it for\n\n- New positioning\n- Repositioning after product or market change\n- Message hierarchy for campaigns or websites\n- Turning research into language the market can understand\n\n## Operating rules\n\n- Use context already present in the conversation before asking for more input.\n- Separate known facts, reasonable assumptions, and unknowns. Do not present assumptions as evidence.\n- When the answer depends on current platform rules, market conditions, pricing, benchmarks, or competitors, verify them with current sources when tools are available.\n- Prefer concrete decisions, examples, and next actions over generic marketing advice.\n- Do not invent campaign performance, customer quotes, research findings, testimonials, rankings, or competitor claims.\n- Keep the requested market, language, funnel stage, audience awareness, budget, and channel constraints visible throughout the work.\n- Start from customer truth, real alternatives, and proof.\n- A positioning statement is an internal decision aid, not necessarily final public copy.\n- Do not claim uniqueness unless evidence supports it.\n- Keep one primary message per audience and buying situation.\n\n## Workflow\n\n1. Select the priority segment and buying situation.\n2. Name the real alternative and why it remains attractive.\n3. Define the customer problem, consequence, trigger, and desired progress.\n4. Identify differentiated value that matters to this segment and attach proof.\n5. Write an internal positioning statement.\n6. Convert it into message hierarchy: primary promise, supporting messages, proof, objection handling, and CTA direction.\n7. Pressure-test for clarity, credibility, relevance, and competitive defensibility.\n\n## Output contract\n\n- Positioning statement\n- Message hierarchy\n- Proof and objection matrix\n- Channel adaptation notes\n\n## Quality gate\n\n- The message is specific to a segment and situation\n- Proof is attached to claims\n- The language could be understood without product jargon\n- The hierarchy can guide copy across channels\n\n## Handoff\n\nIf the task is part of a larger marketing request, return the completed deliverable plus the evidence or decisions the next PrePilot skill needs. Do not repeat upstream analysis unless it changes the result.\n"
}