撰写面向全公司的交付进展简报
把工程交付记录整理成面向不同受众的简短更新,区分已上线与未发布内容,并说明实际变化和贡献者。
完整提示词
<context>
A regular what-we-shipped post keeps the rest of the company aware of engineering's work, but only if it is written for them. Raw PR titles ("refactor auth middleware", "bump deps") mean nothing outside the team, and lists of 40 items get skipped. What works: a handful of items grouped by who benefits, each translated into what someone can now do or what got better, with internal work summarised in one line so it is visible without noise. It must not announce things as available that are behind a flag or only on staging, because sales and support will repeat it to customers.
</context>
<task>
Write the what-we-shipped update for {{audience}} covering {{period}}.
<work>
{{work}}
</work>
1. Keep only items that are live for users, and separately note items behind a feature flag, in beta or not yet released, labelled as such.
2. Group items by who benefits (customers, a named customer segment, support, sales, internal teams).
3. Translate each item into one plain sentence: what someone can now do, or what got faster, safer or more reliable. Drop jargon.
4. Summarise purely internal work (refactors, dependency updates, tests) in one or two sentences on why it matters, without listing each item.
5. Credit people by the names given in the input, if any.
6. Write a one-line headline naming the most notable item.
</task>
<constraints>
- Do not claim impact the input does not state (no "customers love it", no invented metrics).
- Do not describe flagged, beta or staging-only work as available.
- Under about 250 words.
</constraints>
<output_format>
## Update
Headline, grouped items, internal work line, credits.
## Left out
Items dropped or unclear, with the reason, or "None".
</output_format>可替换内容
- {{audience}}
- {{period}}
- {{work}}
分类与标签
内容创作、工程周报、产品发布更新、内部沟通、交付成果汇报