编写变更审批申请与回滚计划
围绕系统变更整理风险、测试证据和执行步骤,生成含回滚安排、影响沟通与待补信息的审批文档。
完整提示词
<context>
Change advisory boards reject or delay requests for the same reasons: the risk rating does not match the description, testing is asserted but not evidenced, the implementation plan has no timings or verification, the rollback plan says "restore from backup" with no idea how long that takes, affected services and users are not listed, and the change overlaps a freeze or another change. A good request lets a reviewer who does not know the system judge the risk in five minutes. Many organisations distinguish standard (pre-approved), normal and emergency changes; a recurring low-risk change may be worth proposing as a standard change.
</context>
<task>
Change: {{change}}
{{#template}}Template or risk matrix: {{template}}{{/template}}
1. Summary: a one-line title, what changes, why now, change type (standard, normal, emergency) with the reason, the requested window, and the requester and implementer roles.
2. Risk assessment: likelihood and impact with reasons, using the template's matrix if given; what could go wrong (list the realistic failure modes), the blast radius, and mitigations. Flag if the stated risk looks understated.
3. Testing evidence: what was tested, where (environment parity with production), with what results, and what could not be tested in advance. Mark missing evidence as a gap.
4. Implementation plan: timed steps with the person or role, pre-checks, verification after each significant step, and the total duration.
5. Rollback plan: trigger conditions, steps, time to roll back, data implications, and the point after which rollback is not possible.
6. Impact and communications: affected services, users and teams, expected downtime or degradation, who is notified before and after, and conflicts with freezes or other changes in the window (ask if unknown).
7. List the questions the board is likely to ask and the answers, or the gaps to fill before submitting.
</task>
<constraints>
- Do not invent test results, timings or approvals; mark gaps.
- Do not downgrade the risk to get approval; if the change is risky, say so and strengthen mitigation.
- Match the organisation's template field names when given.
{{> output/uncertainty}}
</constraints>
<output_format>
## Summary
## Risk assessment
## Testing evidence
## Implementation plan
Table: Time | Step | Owner | Verification.
## Rollback plan
## Impact and communications
## Questions the board will ask
</output_format>可替换内容
- {{change}}
- {{#template}}
- {{template}}
- {{/template}}
- {{> output/uncertainty}}
分类与标签
办公效率、变更审批、风险评估、回滚计划、运维文档