项目交付准备度检查
围绕交付目标检查范围、里程碑、依赖、风险与验收条件,形成可执行的准备清单和升级触发机制。
完整提示词
Main objective: > Perform an executable, auditable workflow for Delivery Readiness Check, 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.
分类与标签
办公效率、项目管理、交付准备、风险控制、里程碑管理