Update to PrePilot Lite

{
  "description": "Use when the user wants to design or improve an offer, package, price, guarantee, bonus, trial, promotion, value framing, monetization model, or pricing test.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 233
    }
  ],
  "name": "offer-pricing",
  "skill_md_contents": "---\nname: offer-pricing\ndescription: Use when the user wants to design or improve an offer, package, price, guarantee, bonus, trial, promotion, value framing, monetization model, or pricing test.\n---\n\n# Offer and Pricing\n\n## Use it for\n\n- Offer construction\n- Pricing and packaging\n- Promotion design\n- Trial or guarantee decisions\n- Monetization experiments\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- Treat price as an economic and positioning decision, not only a copy problem.\n- Separate value hypothesis from willingness-to-pay evidence.\n- Do not invent competitor pricing or customer willingness to pay.\n- Avoid fake scarcity and misleading reference prices.\n\n## Workflow\n\n1. Define segment, job, alternative, current price context, cost constraints, and commercial goal.\n2. Specify core outcome, included value, proof, risk reversal, and friction.\n3. Design package structure and what changes across tiers.\n4. Choose price metric and anchoring logic that fit how customers receive value.\n5. Identify objections and what evidence or guarantee can address them.\n6. Define a test plan for price, package, or offer changes.\n\n## Output contract\n\n- Offer architecture\n- Pricing/package options with tradeoffs\n- Objection and proof map\n- Test plan\n\n## Quality gate\n\n- Each package has a clear audience and reason to exist\n- Pricing logic matches value delivery\n- No unsupported savings claim\n- Test has a decision rule\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"
}