编写团队职责与协作说明
整理团队负责范围、需求入口、响应时限与值班安排,生成便于跨团队查阅的说明页面。
完整提示词
<context>
A team README is the page other teams land on when they need something from you, so it should answer their questions, not describe your internal rituals (that is the charter). The questions are always the same: is this yours, how do I ask, how fast will you answer, what counts as urgent and how do I page you, what are you working on and when could my request fit in. Good READMEs are short, put the routing information above the fold, define "urgent" concretely, give a request template so asks arrive with context, and are dated with an owner so they do not rot.
</context>
<task>
Write the team README.
<team>
{{team}}
</team>
{{#pain_points}}
<pain_points>
{{pain_points}}
</pain_points>
{{/pain_points}}
1. Open with one sentence on what the team does and a "Need something?" block: where to ask, where to file, how to page for incidents.
2. List what the team owns (services, repos, dashboards) and, just as useful, look-alike things it does not own and who does, if known.
3. Explain how to request work: the queue, a short request template (what, why, by when, impact), how requests are prioritised and the planning cadence.
4. State response expectations by type: incidents, bugs, questions, feature requests. Define what counts as urgent with examples.
5. Describe on-call: hours, how to page, what on-call handles and what waits.
6. Add current priorities and how to find the roadmap.
7. Add an FAQ{{#pain_points}} built from the pain points{{/pain_points}}.
8. End with a "last reviewed" line and owner placeholder.
</task>
<constraints>
- Use only names, channels, systems and commitments from the input; placeholders for anything missing, listed at the end.
- No personal phone numbers or private contact details; use rotations and channels.
- Keep it to one screen above the fold and scannable; tables for ownership and response times.
- Friendly but firm about the intake route; no passive-aggressive wording.
</constraints>
<output_format>
## README
The page in Markdown.
## Placeholders
What to fill before publishing.
</output_format>可替换内容
- {{team}}
- {{#pain_points}}
- {{pain_points}}
- {{/pain_points}}
分类与标签
办公效率、团队说明文档、跨团队协作、需求受理、值班安排