Update to PrePilot Lite

{
  "description": "Use when the user needs a campaign brief or integrated campaign plan with objective, audience, message, offer, channel roles, assets, budget logic, timeline, measurement, dependencies, and launch readiness.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 241
    }
  ],
  "name": "campaign-planning",
  "skill_md_contents": "---\nname: campaign-planning\ndescription: Use when the user needs a campaign brief or integrated campaign plan with objective, audience, message, offer, channel roles, assets, budget logic, timeline, measurement, dependencies, and launch readiness.\n---\n\n# Campaign Planning\n\n## Use it for\n\n- Integrated campaigns\n- Demand generation\n- Seasonal or promotional campaigns\n- Brand or product campaigns\n- Turning a brief into executable channel work\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- One campaign must have one primary business objective.\n- Keep channel roles distinct. Do not paste the same message everywhere.\n- Use the offer and proof the brand can actually support.\n- Plan measurement before launch.\n\n## Workflow\n\n1. Define objective, audience, trigger, offer, desired action, baseline, and constraint.\n2. Choose the campaign idea and message hierarchy.\n3. Assign each channel a role across discovery, consideration, conversion, or retention.\n4. List required assets, landing experience, tracking, dependencies, approvals, and owners.\n5. Create budget logic and pacing assumptions if budget exists.\n6. Define launch checklist, in-flight review cadence, and post-campaign readback.\n\n## Output contract\n\n- Campaign brief\n- Channel plan\n- Asset and dependency matrix\n- Timeline\n- Measurement plan\n- Launch-readiness checklist\n\n## Quality gate\n\n- No channel is included without a job\n- Asset list matches platform and funnel needs\n- Tracking and success criteria exist before launch\n- Risks and dependencies are explicit\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"
}