Update to Operator Powers

{
  "name": "digital-product-launch-builder",
  "description": "Build a coordinated launch for a defined digital product, course, template, membership, workshop, or resource, including readiness, messages, calendar, assets, and measures.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 248
    }
  ],
  "skill_md_contents": "---\nname: digital-product-launch-builder\ndescription: Build a coordinated launch for a defined digital product, course, template, membership, workshop, or resource, including readiness, messages, calendar, assets, and measures.\n---\n\n# Digital Product Launch Builder\n\nTurn a defined product into a launch the operator can actually run, measure, and adapt.\n\n## Job contract\n\n- Owns: coordinated launch of a defined digital product.\n- Does not own: defining what is sold (`offer-builder`) or isolated content transformation (`content-repurposing`).\n- Required input: product, buyer, promise, price or pricing status, delivery method, and launch constraints.\n- Finished deliverable: readiness gate, launch calendar, complete core messages, measurement plan, and contingency rules.\n\n## Workflow\n\n1. Run readiness: product delivery, checkout, support, refund terms, legal claims, proof, capacity, and buyer clarity.\n2. If the offer is not defined, pause launch design and route to `offer-builder`.\n3. Choose a launch type appropriate to audience and capacity: quiet release, waitlist, live event, email-led, content-led, partner, or evergreen opening.\n4. Map phases: evidence gathering, anticipation, opening, objections, decision window, delivery, review.\n5. Build the message spine and channel sequence. Every asset must perform a distinct job.\n6. Set measures for attention, intent, conversion, revenue, refunds, and delivery quality.\n7. Add stop, extend, and change rules so results guide the launch.\n\n## Output\n\n```markdown\n# Digital Product Launch\n\n## Readiness Gate\n[Ready, blocked, owner, fix]\n\n## Launch Strategy\n[Buyer, product, promise, type, dates, target]\n\n## Message Spine\n[Problem, belief, mechanism, proof, offer, objections]\n\n## Launch Calendar\n| Timing | Channel | Asset | Job | CTA | Owner |\n\n## Core Assets\n[Complete drafts for the essential sequence]\n\n## Measurement And Decisions\n[Metrics, thresholds, stop/change rules]\n\n## Delivery And Review\n[Customer experience, support, retrospective]\n```\n\n## Guardrails\n\n- Never invent demand, testimonials, revenue targets presented as forecasts, scarcity, or deadlines.\n- Do not schedule, publish, email, spend, or change live checkout settings without explicit approval.\n- Keep the launch smaller than the operator's delivery capacity.\n"
}