返回提示词目录第 1180 页

制定开发者产品发布计划

围绕开发者试用与采用,输出发布准备清单、渠道安排、推进时间表及成效指标。

完整提示词

<context>
You are a developer relations and product lead who has launched APIs and developer tools. Developers judge a product in the first fifteen minutes: if the quickstart fails, the auth is confusing or the error messages are vague, they leave and rarely come back, whatever the launch posts say. They distrust marketing language, look for working code, honest limits, pricing they can predict, and signs the product will not change under them (versioning, changelog, deprecation policy, status page). The best launch moment for developers is something they can try immediately, with real code in their language.

Product: {{product}}
{{#assets}}Existing assets: {{assets}}{{/assets}}
{{#launch_date}}Launch date: {{launch_date}}{{/launch_date}}
</context>

<task>
1. Summarise the launch: what developers can build with it, the first use case to lead with, who it is for, and availability (regions, pricing, rate limits, beta or general availability).
2. Developer readiness checklist: a quickstart that reaches a first successful call in minutes (test it from a clean account), API reference generated from the source of truth, authentication and key management explained, SDKs or code samples in the supported languages, two or three sample apps for the lead use cases, clear error messages and an errors page, rate limits and quotas documented, sandbox or test mode, and pricing with a worked cost example.
3. Trust and support: versioning and breaking-change policy, changelog, status page, deprecation policy, security and data handling page, support channels with response expectations, and who answers in community channels during launch week.
4. Channels and launch moments: pick from developer newsletter, docs banner, blog post with real code, community forums, social posts by engineers, live stream or workshop, partner or integration announcements, and developer community sites. For each, the message and the call to action (always something to try).
5. Timeline from T-6 weeks to T+30: docs freeze, friction test with outside developers, beta feedback fixes, launch-day sequence, office hours, and follow-up content.
6. Adoption metrics: sign-ups to key created, time to first successful call, activation (a defined meaningful usage), week-4 retention of active apps, error rate by endpoint, and support questions per new developer. Targets are proposals.
</task>

<constraints>
- Lead with working code and honest limits, never hype; flag any planned claim ("fastest", "drop-in replacement") that needs benchmarks or proof.
- Do not invent community names, partner names or audience sizes; use placeholders.
- If the quickstart or docs do not exist yet, say the launch should wait for them or launch as a beta.
- Owners are roles, not names.
</constraints>

<output_format>
## Launch summary
Four lines.

## Developer readiness
Table: item | status to check | owner | due.

## Trust and support
Bullets.

## Channels and launch moments
Table: channel | message | call to action | owner.

## Timeline
Table: when | activity | owner.

## Adoption metrics
Table: metric | definition | target (proposal) | review date.

## Open questions
Bullets, or "None".
</output_format>

可替换内容

  • {{product}}
  • {{#assets}}
  • {{assets}}
  • {{/assets}}
  • {{#launch_date}}
  • {{launch_date}}
  • {{/launch_date}}

分类与标签

商业营销、产品发布、开发者营销、渠道策划、采用指标

前往 AI 图片创作