<!-- تعليمات النموذج الذكي: املأ خطة عمل التخفيف من المخاطر بناءً على
سياق المشروع.

تعريف وسياق:
خطة عمل التخفيف من المخاطر هي الالتزام بما سيُعمل بشأن مخاطرة مسماة: المعالجة
التي تُعطى لها، والخطوات التي تنفذ هذه المعالجة، وما تكلّفه تلك الخطوات، والدرجة
التي يتوقع المشروع بلوغها بعد إنجازها. وهي ناتج عن عملية تخطيط استجابات
المخاطر، ووجودها حتى لا تبقى مخاطرة قد تم التعرف عليها موجودة بلا جواب.

يستقبل من:
*  سجل المخاطر
*  خطة إدارة المخاطر
*  مصفوفة استجابة المخاطر

يقدم معلومات إلى:
*  سجل المخاطر
*  سجل التغيير، حين تغيّر المعالجة خط الأساس
*  تقرير حالة المشروع، لأن المخاطرة المقبولة واقعة من واقع الحالة

ملاحظات التخصص:
*  خطط للمخاطر التي درجتها تستحق الجهد فقط. فخطة لكل مخاطرة مسجلة تبذل
  الجهد نفسه على مخاطرة كانت ستُقبل على أي حال.
*  اكتب الدرجة المستهدفة قبل الخطوات لا بعدها. فالهدف هو ما يجعل الخطوات
  قابلة للفحص، وإذا كُتب أخيرًا صار وصفًا لما حدث لا التزامًا به.
*  أعطِ المخاطرة المقبولة سببًا واسمًا. فالقبول هو الاستجابة الوحيدة التي
  هي قرار لا عمل، ولذلك هي الأكثر تركًا بلا تسجيل.

المحاذاة:
يجب أن يتسق خطة عمل التخفيف من المخاطر مع:
*  سجل المخاطر
*  خطة إدارة المخاطر
*  تدقيق المخاطر، الذي يبحث عن الاستجابات التي خططت ولم تُنفّذ

توجيهات استيفاء الأقسام:
*  1. تقييم المخاطرة: سمِّ المخاطرة كما يحملها السجل، ثم أعطِ الدرجة حاصل
  ضرب الاحتمالية في الأثر مع كتابة العاملين معًا.
*  2. خطة التخفيف: اذكر المعالجة، والخطوات التي تنفذها لكل خطوة مالك وتاريخ،
  وما تكلّفه، والدرجة التي تتوقع الخطة بلوغها.
-->


<h3 align="left">{{اسم_الشركة}}</h3>
<h2 align="left">{{اسم_المشروع}} - {{معرف_المشروع}}</h2>
<h1 align="center">خطة عمل التخفيف من المخاطر</h1>

| **تاريخ الإعداد:** {{التاريخ_الحالي}} | **مدير المشروع:** {{اسم_مدير_المشروع}} | **إعداد:** {{معد_الوثيقة}} |
| ---: | ---: | ---: |

---

## 1. تقييم المخاطرة

| معرف المخاطرة وعنوانها | درجة المخاطرة الحالية |
| ---: | ---: |
| [ أضف التفاصيل... ] | [ أضف التفاصيل... ] |

## 2. خطة التخفيف

| استراتيجية التخفيف | خطوات العمل التفصيلية | متطلبات الموارد | درجة المخاطرة المستهدفة |
| ---: | ---: | ---: | ---: |
| [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] |

### الاعتماد والموافقات

| الدور | الاسم | التوقيع | التاريخ |
| ---: | ---: | ---: | ---: |
| **مالك إجراء التخفيف** | {{اسم_مالك_الإجراء}} | _______________________ | [.... -.... -.... ] |
| **مدير المخاطر** | {{اسم_مدير_المخاطر}} | _______________________ | [.... -.... -.... ] |
| **مدير المشروع** | {{اسم_مدير_المشروع}} | _______________________ | [.... -.... -.... ] |
---

<div align="left" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>سجل التدقيق الإلكتروني: Hash SHA256: {{رمز_تجزئة_التدقيق_SHA256}}</span> <br>
 <strong>النموذج:</strong> خطة عمل التخفيف من المخاطر | <strong>المرجع:</strong> PMO-04.08.07 <br>
 <i>تاريخ الإنشاء: {{وقت_الإنشاء}}, بواسطة <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">تسليمات</a></i>
</div>
</div>

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://tasleemat.pmo/schemas/completed/PMO-04.08.07.schema.json",
  "title": "Completed RISK MITIGATION ACTION PLAN Data Contract",
  "description": "Additive structural schema validating completed RISK MITIGATION ACTION PLAN artifact data payloads (PMO-04.08.07).",
  "type": "object",
  "properties": {
    "artifact_id": {
      "type": "string",
      "const": "PMO-04.08.07"
    },
    "metadata": {
      "type": "object",
      "properties": {
        "project_name": {
          "type": "string",
          "minLength": 1
        },
        "project_code": {
          "type": "string"
        },
        "date_prepared": {
          "type": "string",
          "format": "date"
        },
        "project_manager": {
          "type": "string",
          "minLength": 1
        },
        "prepared_by": {
          "type": "string",
          "minLength": 1
        },
        "version": {
          "type": "string"
        },
        "status": {
          "type": "string",
          "enum": [
            "draft",
            "baselined",
            "in_review",
            "approved"
          ]
        }
      },
      "required": [
        "project_name",
        "date_prepared",
        "project_manager",
        "prepared_by"
      ]
    },
    "risk_assessment": {
      "type": "object",
      "properties": {
        "risk_id_and_title": {
          "type": "string",
          "minLength": 1,
          "description": "The identifier and title of the risk exactly as the risk register carries them, so this plan can be joined back to the register. A title written here that differs from the register's is the defect that makes the two documents disagree about what is being planned for."
        },
        "current_risk_score": {
          "type": "string",
          "minLength": 1,
          "description": "The probability multiplied by the impact, each on the scale the register uses, with both factors shown rather than only the product. A score given on its own hides the reason for it, and a score whose factors cannot be read back cannot be recalculated when one of them changes."
        }
      },
      "required": [
        "risk_id_and_title",
        "current_risk_score"
      ]
    },
    "mitigation_plan": {
      "type": "object",
      "properties": {
        "mitigation_strategy": {
          "type": "string",
          "minLength": 1,
          "description": "Which of the four treatments the risk is given: avoid, transfer, mitigate, or accept. Accept is a decision that needs a reason, so an accepted risk carries the reason and the name of whoever accepted it."
        },
        "detailed_action_steps": {
          "type": "string",
          "minLength": 1,
          "description": "The plan as ordered steps, each with an owner and a date, so that the plan can be read as work rather than as intent. A step with no owner is a wish, and a step with no date is a step that never starts."
        },
        "resource_requirements": {
          "type": "string",
          "minLength": 1,
          "description": "What executing the plan costs and who has to be assigned to it: the budget, the people, and the time. Stated so the request can be approved against something, rather than argued in a meeting where no one can check it."
        },
        "target_risk_score": {
          "type": "string",
          "minLength": 1,
          "description": "The score the plan is expected to reach, with the assumptions it depends on. A target written without saying which steps deliver it cannot be checked afterwards, which leaves no way to know whether the plan worked."
        }
      },
      "required": [
        "mitigation_strategy",
        "detailed_action_steps",
        "resource_requirements",
        "target_risk_score"
      ]
    }
  },
  "required": [
    "artifact_id",
    "metadata",
    "risk_assessment",
    "mitigation_plan"
  ]
}

{
  "form_name": "RISK MITIGATION ACTION PLAN",
  "document_reference": "PMO-04.08.07",
  "_llm_instructions": "Populate the fields of 'RISK MITIGATION ACTION PLAN' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-04.08.07.",
  "project_title": "",
  "date_prepared": "",
  "fields": {
    "f01_Risk_ID_and_Title": {
      "section": "Risk Assessment",
      "label": "Risk ID and Title",
      "guidance": "The identifier and title of the risk exactly as the risk register carries them, so this plan can be joined back to the register. A title written here that differs from the register's is the defect that makes the two documents disagree about what is being planned for.",
      "value": ""
    },
    "f02_Current_Risk_Score": {
      "section": "Risk Assessment",
      "label": "Current Risk Score",
      "guidance": "The probability multiplied by the impact, each on the scale the register uses, with both factors shown rather than only the product. A score given on its own hides the reason for it, and a score whose factors cannot be read back cannot be recalculated when one of them changes.",
      "value": ""
    },
    "f03_Mitigation_Strategy": {
      "section": "Mitigation Plan",
      "label": "Mitigation Strategy",
      "guidance": "Which of the four treatments the risk is given: avoid, transfer, mitigate, or accept. Accept is a decision that needs a reason, so an accepted risk carries the reason and the name of whoever accepted it.",
      "value": ""
    },
    "f04_Detailed_Action_Steps": {
      "section": "Mitigation Plan",
      "label": "Detailed Action Steps",
      "guidance": "The plan as ordered steps, each with an owner and a date, so that the plan can be read as work rather than as intent. A step with no owner is a wish, and a step with no date is a step that never starts.",
      "value": ""
    },
    "f05_Resource_Requirements": {
      "section": "Mitigation Plan",
      "label": "Resource Requirements",
      "guidance": "What executing the plan costs and who has to be assigned to it: the budget, the people, and the time. Stated so the request can be approved against something, rather than argued in a meeting where no one can check it.",
      "value": ""
    },
    "f06_Target_Risk_Score": {
      "section": "Mitigation Plan",
      "label": "Target Risk Score",
      "guidance": "The score the plan is expected to reach, with the assumptions it depends on. A target written without saying which steps deliver it cannot be checked afterwards, which leaves no way to know whether the plan worked.",
      "value": ""
    }
  }
}