Update to PrePilot Lite

{
  "description": "Use when the user needs a product launch, feature launch, go-to-market plan, launch tier, readiness checklist, message house, channel mobilization, sales enablement, launch timeline, or post-launch readback.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 232
    }
  ],
  "name": "launch-gtm",
  "skill_md_contents": "---\nname: launch-gtm\ndescription: Use when the user needs a product launch, feature launch, go-to-market plan, launch tier, readiness checklist, message house, channel mobilization, sales enablement, launch timeline, or post-launch readback.\n---\n\n# Launch and GTM\n\n## Use it for\n\n- Product and feature launches\n- GTM planning\n- Launch tier and scope\n- Readiness review\n- Post-launch learning\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- Scale launch effort to the importance and evidence behind the release.\n- A launch is a coordinated market event, not simply a list of posts.\n- Do not create proof that the product has not earned.\n- Include product readiness, support, sales, measurement, and operational dependencies where relevant.\n\n## Workflow\n\n1. Define launch objective, audience, product truth, release scope, availability, market timing, and business risk.\n2. Classify launch tier and required coordination.\n3. Build positioning, message hierarchy, proof, offer, and launch story.\n4. Plan channel roles, assets, sales/support enablement, PR/community activity, and internal readiness.\n5. Create launch readiness gate with blockers, owners, and go/no-go criteria.\n6. Define launch-day monitoring and post-launch readback.\n\n## Output contract\n\n- Launch brief\n- Tier and scope rationale\n- Message house\n- Channel/asset timeline\n- Readiness checklist\n- Post-launch measurement plan\n\n## Quality gate\n\n- Claims match shipped product\n- Dependencies are visible\n- Launch scope matches business importance\n- There is a post-launch learning loop\n\n## Market-entry and motion selection\n\nBefore building the launch calendar, decide where and how the product should enter the market:\n\n- Choose an initial segment using evidence about urgency, buying ability, access, competitive fit, and reference value.\n- Compare GTM motions such as inbound, outbound, paid acquisition, community, partnerships, account-based work, and product-led adoption by economics and buyer behavior rather than popularity.\n- Pick a primary motion and only the supporting motions that reinforce it. State why other plausible motions are deferred.\n- Revisit the motion mix when ACV, sales cycle, product maturity, team capacity, or channel evidence changes.\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"
}