返回提示词目录第 1425 页

梳理跨团队系统归属与职责

核对代码、告警及部署信息,整理系统责任表,标出归属空缺与争议并提出维护机制。

完整提示词

<context>
Ownership gaps show up during incidents ("who owns this cron job?"), audits and reorganisations. The sources disagree: the repo's CODEOWNERS names a team that was dissolved, alerts route to a person who left, the cloud account is tagged with a project nobody remembers, and the on-call schedule covers services but not the batch jobs and databases behind them. A useful map reconciles these sources, records ownership by team (never by individual), and treats "who is paged when it breaks" as the real test of ownership. Orphaned systems are often the riskiest: unpatched, unmonitored, and still in the critical path.
</context>

<task>
Inventory: {{inventory}}
{{#trigger}}Trigger: {{trigger}}{{/trigger}}

1. If you can read repositories or configuration, check CODEOWNERS, service manifests, alert routing and deployment configs to fill gaps, and say which source each fact came from. Do not change any file.
2. Build the map: every system (services, scheduled jobs, queues, databases, data pipelines, repos, dashboards, cloud accounts) with the owning team according to each source, the on-call rotation that is paged, criticality if known, and status (active, deprecated, unknown).
3. Find orphaned systems: no owning team, owner is a dissolved team or a departed person, or no one paged when it fails.
4. Find disputed or split ownership: sources disagree, two teams claim it, or code and runtime are owned by different teams.
5. Propose an owner for each gap, with a reason (who changes it most, who depends on it, who has the knowledge), and flag systems that may be candidates for decommissioning instead.
6. Define what owning means: on-call, patching and upgrades, cost, documentation, deprecation decisions.
7. Keeping it current: one source of truth, ownership checked on reorgs and team changes, a quarterly review, and alerts on systems with no owner.
</task>

<constraints>
- Do not invent systems or owners; mark unknowns as unknown and list how to find out.
- Ownership is by team, not individual.
- Proposals are for discussion with the teams; do not present them as decisions.
{{> output/uncertainty}}
</constraints>

<output_format>
## Ownership map
Table: System | Type | Owner per source | Paged rotation | Criticality | Status.
## Orphaned systems
## Disputed or split ownership
## Proposed owners
Table: System | Proposed team | Reason | Or decommission?
## What owning means
## Keeping it current
</output_format>

可替换内容

  • {{inventory}}
  • {{#trigger}}
  • {{trigger}}
  • {{/trigger}}
  • {{> output/uncertainty}}

分类与标签

办公效率、团队分工、系统台账、值班责任、归属审查

前往 AI 图片创作