Update to PrePilot Lite

{
  "description": "Use when the user needs lifecycle email strategy, welcome, nurture, activation, onboarding, abandoned flow, post-purchase, retention, win-back, newsletter, cold outbound, segmentation, frequency, or sequence copy.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 233
    }
  ],
  "name": "email-lifecycle",
  "skill_md_contents": "---\nname: email-lifecycle\ndescription: Use when the user needs lifecycle email strategy, welcome, nurture, activation, onboarding, abandoned flow, post-purchase, retention, win-back, newsletter, cold outbound, segmentation, frequency, or sequence copy.\n---\n\n# Email Lifecycle\n\n## Use it for\n\n- Lifecycle strategy\n- Automated sequences\n- Newsletter planning\n- Retention and win-back\n- Cold outbound when appropriate\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- Map email to a customer state and next useful action.\n- Respect consent, preference, frequency, and deliverability constraints.\n- Do not use deceptive subject lines or fake reply/forward patterns.\n- Separate marketing lifecycle and cold outbound requirements when they have different compliance obligations.\n\n## Workflow\n\n1. Define audience state, trigger, desired behavior, offer/value, segmentation, timing constraints, and consent context.\n2. Design sequence logic before writing individual emails.\n3. Assign one job to each message and specify the next state.\n4. Write subject, preview, body, proof, CTA, and fallback path.\n5. Set frequency, suppression, exit conditions, and experiment ideas.\n6. Define delivery, engagement, conversion, and downstream business metrics.\n\n## Output contract\n\n- Lifecycle map\n- Sequence table\n- Email copy when requested\n- Segmentation and suppression logic\n- Measurement and test plan\n\n## Quality gate\n\n- Each message advances a state\n- No sequence exists only to increase send volume\n- Consent and exit logic are clear\n- Success is measured beyond opens\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"
}