返回提示词目录第 1410 页

制定项目恢复与交付执行计划

围绕项目目标、责任人、依赖和风险梳理恢复路径,并生成交付矩阵、执行步骤及复核触发条件。

完整提示词

Main objective:

> Perform an executable, auditable workflow for Project Recovery Plan, with a clear objective, owner, assumptions, dependencies, risks and review triggers.

## 1. OPERATING CONTEXT
Define objective, scope, owner, stakeholders, constraints, deadline, dependencies, current state, available capacity and success criteria.

## 2. DOMAIN STANDARD
Project execution should maintain a single view of scope, milestones, dependencies, risks, decisions and changes. Status exists to support action, not reporting theater.

## 3. INTEGRITY CHECKS
- scope has inclusions/exclusions
- milestones represent outcomes
- dependencies have owners
- risks include trigger/response
- changes update cost/time/scope
- status highlights decisions/blockers
- delivery has acceptance criteria
- retrospective produces owned actions

## 4. OPERATING CARD
```text
Objective:
Owner:
Scope:
Dependency:
Assumption:
Risk:
Decision:
Next action:
Deadline/trigger:
Success evidence:
Review date:
```

## 5. REQUIRED MATRICES
### Delivery Matrix
| Milestone | Outcome | Owner | Dependency | Date | Status | Acceptance |
|---|---|---|---|---|---|---|

### Risk/Change Matrix
| Item | Trigger | Impact | Owner | Response | Decision |
|---|---|---|---|---|---|

## 6. FAILURE MODES
Avoid ownerless work, hidden dependencies, vague goals, unbounded scope, excessive process, automation without controls, status reporting with no decision value and plans that ignore capacity.

## 7. REQUIRED OUTPUT
1. Objective and scope.
2. Owner/stakeholders.
3. Dependencies and assumptions.
4. Risks/controls.
5. Required matrices.
6. Execution sequence.
7. Review cadence.
8. Stop/change/escalation triggers.

End with **Operating Integrity Check** confirming every active item has ownership, a next action and a review mechanism.

分类与标签

办公效率、项目恢复、里程碑管理、风险跟踪

前往 AI 图片创作