القائمة
Record delivery decisions and dependency handoffs with acceptance verification and escalation guidance.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | delivery-commitment-control |
| description | Record delivery decisions and dependency handoffs with acceptance verification and escalation guidance. |
Use this skill when formalizing a delivery-affecting decision, opening or closing a cross-party dependency handoff, or escalating one of those records.
For each delivery-affecting decision, record:
Use a handoff record whenever one party supplies work, information, access, a decision, or a service that another party needs to continue delivery.
For each handoff, record:
pending until assessment, accepted when every criterion is met, or rejected with unmet criteria recorded.Do not treat a handoff as committed when any required field is missing. Record unresolved ownership, acceptance criteria, or timing as a planning risk.
Set verification status to pending until the receiver assesses the deliverable. Set it to accepted only when every acceptance criterion is met; otherwise set it to rejected and record the unmet criteria.
Before marking a handoff complete, confirm that its verification status is accepted.
Raise a critical-path escalation when an unresolved decision or unaccepted handoff threatens an affected commitment. Include the decision or handoff record, unresolved fields or unmet acceptance criteria, accountable decision owner or provider and receiver, effective or needed-by date, latest safe resolution date, and immediate next action.
Complete one record per delivery-affecting decision. Fill every field; mark an unknown value as unresolved.
| Field | Record |
|---|---|
| Decision | |
| Decision owner | |
| Effective date | |
| Affected commitments | |
| Impact | |
| Follow-up actions | |
| Linked control record |
Complete one record per dependency handoff. Fill every field and update verification status as the receiver assesses the deliverable.
| Field | Record |
|---|---|
| Provider | |
| Receiver | |
| Deliverable | |
| Acceptance criteria | |
| Needed-by date | |
| Verification status | |
| Linked plan or change record |
Coordinate delivery commitments, risks, status reporting, and controlled changes.
Reflect across Work History and improve memory, playbooks, or reusable skills.
Decide whether a Contoso Outdoors support case requires escalation. Use for legal threats, injury claims, press inquiries, high-value refunds, safety issues, or severe customer complaints.
Decide when user profile facts may be proposed, confirmed, stored, or rejected. Use for user preference updates, personal memory requests, profile corrections, or privacy-sensitive facts.
Apply Contoso Outdoors support tone, response formatting, and closing style. Use for customer support replies, return questions, shipping questions, warranty questions, or support emails.