撰写工程团队季度复盘报告
把团队笔记整理为面向指定受众的季度报告,呈现目标达成、交付成效及下季资源诉求。
完整提示词
<context>
A quarterly review is how an engineering team earns trust and resources. It goes wrong in familiar ways: a changelog of tickets instead of outcomes, vanity metrics without baselines, slipped goals buried or spun, platform and debt work described in terms leaders cannot value, and no clear ask, so nothing changes. Leaders reading it want to know: did we get what we planned, what did it change for users or the business, is the system healthy, is the team healthy, and what do you need from me. This review covers {{quarter}} for a {{audience}} audience.
</context>
<task>
<notes>
{{notes}}
</notes>
1. Summary: three to five sentences, bottom line first, including the most important miss if there is one.
2. Outcomes against goals: each goal set at the start of the quarter with its result as met, partly met or missed, the number against the target and baseline, and one line on why. Do not drop goals that were missed or abandoned; say so and why.
3. What shipped: group work into three to six themes; for each, the user or business effect (with the metric if given) rather than a ticket list. Translate platform and debt work into effects (deploy time cut from 40 to 12 minutes, so fixes reach users the same day).
4. Reliability and operations: SLO attainment, incidents by severity with one line on the main one and its follow-ups, on-call load and trend. Use only numbers given.
5. Team and tech health: headcount changes, hiring, attrition risk only at the level appropriate for the audience, tech debt paid and added, risks building up (single points of knowledge, unsupported dependencies).
6. Next quarter: two to four bets with the expected outcome and how it will be measured, plus what you will not do.
7. Asks: specific decisions, people, budget or help from other teams, each with the date it is needed and the impact if not.
8. Adapt to the audience: leadership gets business effects and asks first, about 600 words; engineering can include technical detail and metrics definitions; cross-functional emphasises user-facing changes and dependencies.
</task>
<constraints>
- Use only facts and numbers from the notes. Mark missing baselines or targets as [X] rather than presenting a number without context.
- Be candid about misses without blame; name causes as conditions (scope grew, dependency late), never individuals.
- Do not disclose personal matters (health, performance issues of named people) even if they are in the notes; describe capacity impact only.
- Keep to the claims the data supports; label estimates as estimates.
</constraints>
<output_format>
## Summary
Three to five sentences.
## Outcomes against goals
Table: goal, target, result, status (met, partly, missed), why.
## What shipped and why it matters
Three to six themed bullets, each effect first.
## Reliability and operations
Short table of metrics (metric, this quarter, last quarter, target) then two to four bullets.
## Team and tech health
Bullets.
## Next quarter
Table: bet, expected outcome, measure. Then "Not doing" bullets.
## Asks
Numbered: ask, from whom, by when, impact if not.
</output_format>可替换内容
- {{quarter}}
- {{audience}}
- {{notes}}
- [X]
分类与标签
办公效率、季度复盘、团队汇报、目标追踪、资源申请