PMO-05.09 Phase 05: Executing
Tier 1 ai

Prompt Library Log

سجل مكتبة الأوامر
tasleemat asset PMO-05.09 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 05: Executing

Sizing Tier Requirements

Tier 1

Validation Contract

This deliverable conforms to a strict companion Draft 2020-12 JSON Schema for automated structural and semantic validation.

tasleemat validate PMO-05.09 ./completed_data.json

Template Markdown (Bilingual)

<!-- LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders based on project context.

Context and Definition:
A prompt library log is the record of the prompts a team has found worth
keeping, kept so that the next time the same question comes up the answer is
already written. Its purpose is reuse: a prompt that solved a problem is
worth more the second time it is used than the effort of writing it again,
and worth more still if the team can see what a good response looked like.
It is the working record of an AI-enabled practice, and it changes as the
practice changes, so each entry carries a version.

It can receive information from:
*   Prompt library of the organisation
*   AI governance plan
*   Model card and fact sheet

It provides information to:
*   Lessons learned register
*   Team onboarding checklist
*   Project status report, when AI use is reported

Tailoring Tips:
*   File the prompt, not its history. The library is read under time pressure,
    and a prompt entered with a paragraph of reasoning about it is a prompt
    nobody opens.
*   Write the expected output before the prompt is used. Deciding what a good
    answer looks like after seeing the answer is not a standard, it is a
    description.
*   Retire what does not work. An entry that has been used and did not help is
    the most valuable line in the log, provided it is marked as such.

Alignment:
The prompt library log should be aligned and consistent with:
*   AI governance plan
*   AI readiness assessment
*   Model card and fact sheet, because a prompt that names a model is only
    reusable while that model is in use

Section Instructions:
*   Prompt Library: for each prompt that has been written and used, give its
    identifier, the use case, the text as it is sent, what a good response
    looks like, and the version and status it currently holds.
-->

<h3 dir="ltr" align="right">{{Company_Name}}</h3>
<h2 dir="ltr" align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 dir="ltr" align="center">PROMPT LIBRARY LOG</h1>

| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |

---

## Prompt Library

| Prompt ID | Use Case | Prompt Text | Expected Output | Status/Version |
| :---: | :--- | :--- | :--- | :--- |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **AI Engineer / Prompt Designer** | {{AI_Engineer_Name}} | _______________________ | [ .... - .... - .... ] |
| **AI Technical Lead** | {{AI_Lead_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
---

<div dir="ltr" align="right" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
  <strong>Template:</strong> PROMPT LIBRARY LOG | <strong>Ref:</strong> PMO-05.09 <br>
  <i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>

User Guide & Practitioner Instructions

Tasleemat Forms Guide

Project Artifact: Prompt Library Log

Document Reference: PMO-05.09

This document provides a comprehensive, professional reference to understand the purpose and effective usage of the Prompt Library Log in alignment with the Tasleemat framework.


1. What?

A table of the prompts in use, one row each: an identifier, the use case, the text as it is actually sent, what a good response looks like, and the version and status it currently holds. The text column is the one that decides whether the log is usable: a prompt filed as a description has to be rewritten before it can be sent.


2. Why?

Because prompts are written repeatedly and rarely remembered, and the cost of a badly written prompt is paid in the review of whatever it produced. A library converts that cost into a lookup. It also converts an individual judgement into a shared one: a prompt that two people use gets better in a way that one person's habit does not, and the expected output column is what lets a team say the improvement happened.


3. When?

Written when a prompt has been used and found worth keeping, and revised whenever the prompt itself is revised. The version belongs in the first entry rather than being added later, because a prompt revised without a version number leaves every earlier result attached to a text that no longer exists.


4. Who?

Kept by whoever uses the prompts, which on an AI-enabled project is the team rather than a single owner. The AI or ML lead signs because that role is where prompts are drawn from and where the ones that do not work get noticed. The data protection officer signs because a prompt is where personal data most often enters a model without being noticed.


Tailoring Tips

  • File the prompt, not its history. The library is read under time pressure, and an entry written with a paragraph of reasoning attached to it is an entry nobody opens.
  • Write the expected output before the prompt is used. Deciding what a good answer looks like after seeing the answer is not a standard, it is a description.
  • Retire what does not work. An entry that was used and did not help is the most valuable line in the log, provided it is marked as one rather than deleted.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

  • Mandatory:
    • Project Management Plan (PMO-04.01.01)
    • Approved Baselines (Scope/Schedule/Cost)
  • Optional / Contextual:
    • Risk Register (PMO-04.08.02)
    • Stakeholder Engagement Plan (PMO-04.10.01)

2. Downstream Dependents

  • Mandatory:
    • Project Status Reports (PMO-06.01)
    • Change Log (PMO-05.04)
    • Lessons Learned Summary (PMO-07.01)
  • Optional / Contextual:
    • Variance Analysis (PMO-06.04)
    • Decision Log (PMO-05.02)

5. How?

To accurately complete the Prompt Library Log, populate the following sections based on the project context (ensuring reference to parameters.md for the general project variables):

  • Prompt ID: A short identifier, so a prompt can be referred to in a meeting without its text being read out. A number is enough if it is the only one in use.
  • Use Case: What the prompt is for, in one line: the task it was written to do and the situation it was written in. A prompt filed without its use case cannot be told apart from another one that reads almost the same.
  • Prompt Text: The prompt as it is actually sent, not a description of it. What is filed here has to be usable by pasting it, because a paraphrase is a different prompt and will behave differently.
  • Expected Output: What a good answer looks like, specifically enough to be checked. This is the column that makes the library auditable: without it there is nothing to compare a later response against.
  • Status/Version: Where the prompt stands, and which version this is. A prompt that has been revised without the version moving leaves every earlier result attached to a text that no longer exists.

Associated Templates


6. Reference Example

A fully completed, gold-standard reference example illustrating this artifact in practice is available:

📖 Completed Example: 05_09_Prompt_Library_Log_Example.md

LLM Generation Prompt & Agent Instructions

Prompt Library Log - LLM Generation Prompt

SYSTEM INSTRUCTIONS: This document is the detailed instruction set for generating the Prompt Library Log. When asked to populate the template, follow the guidance for each section below to produce the requested content. Refer to parameters.md for the general project variables.

Context and Definition: The record of the prompts a team has found worth keeping, kept so that the next time the same question comes up the answer is already written. Its purpose is reuse: a prompt that solved a problem is worth more the second time it is used than the effort of writing it again, and worth more still if the team can see what a good response looked like. It is the working record of an AI-enabled practice, and that practice changes, so each entry carries a version.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Project Management Plan (PMO-04.01.01), Approved Baselines (Scope/Schedule/Cost) * Optional: Risk Register (PMO-04.08.02), Stakeholder Engagement Plan (PMO-04.10.01) * Downstream Dependents: * Mandatory: Project Status Reports (PMO-06.01), Change Log (PMO-05.04), Lessons Learned Summary (PMO-07.01) * Optional: Variance Analysis (PMO-06.04), Decision Log (PMO-05.02)


Prompt Library

Prompt ID

Instructions: A short identifier, so a prompt can be referred to in a meeting without its text being read out. A number is enough if it is the only one in use.

Generated Value: [ Add details... ]

Use Case

Instructions: What the prompt is for, in one line: the task it was written to do and the situation it was written in. A prompt filed without its use case cannot be told apart from another one that reads almost the same.

Generated Value: [ Add details... ]

Prompt Text

Instructions: The prompt as it is actually sent, not a description of it. What is filed here has to be usable by pasting it, because a paraphrase is a different prompt and will behave differently.

Generated Value: [ Add details... ]

Expected Output

Instructions: What a good answer looks like, specifically enough to be checked. This is the column that makes the library auditable: without it there is nothing to compare a later response against.

Generated Value: [ Add details... ]

Status/Version

Instructions: Where the prompt stands, and which version this is. A prompt that has been revised without the version moving leaves every earlier result attached to a text that no longer exists.

Generated Value: [ Add details... ]


PMO-05.09 Phase 05: Executing Realistic Case Study Benchmark
Date Prepared
2026-03-15
Project Manager
Faisal Al-Harbi, PMP
Prepared By
Faisal Al-Harbi, PMP (Senior Project Manager)

Prompt Library Log (Reference Example)

🏆 Gold Standard Reference Example: This document illustrates a fully completed, production-grade artifact adhering to the Tasleemat PMO Framework (PMO-05.09). All company names, project references, and figures are realistic fictional simulations.


Apex Global Solutions

Apex Unified Cloud ERP & Supply Chain Modernization - PRJ-2026-ERP-01

PROMPT LIBRARY LOG


Prompt Library

Prompt ID Use Case Prompt Text Expected Output Status/Version
INIT-01 Approved and aligned with Apex Global Solutions governance baseline Approved and aligned with Apex Global Solutions governance baseline Approved and aligned with Apex Global Solutions governance baseline In Progress
REQ-02 Approved and aligned with Apex Global Solutions governance baseline Approved and aligned with Apex Global Solutions governance baseline Approved and aligned with Apex Global Solutions governance baseline Completed
ACT-03 Approved and aligned with Apex Global Solutions governance baseline Approved and aligned with Apex Global Solutions governance baseline Approved and aligned with Apex Global Solutions governance baseline Planned

Sign-off and Approvals

Role Name Signature Date
AI Engineer / Prompt Designer Eng. Layth Al-Husseini (Senior AI/ML Engineer) [Electronically Signed] 2026-03-18
AI Technical Lead Dr. Rayan Al-Sulaiman (Lead AI & Data Scientist) [Electronically Signed] 2026-03-18
Project Manager Faisal Al-Harbi, PMP [Electronically Signed] 2026-03-18
---
Template: PROMPT LIBRARY LOG | Ref: PMO-05.09
Generated on: 2026-03-15 10:00 UTC, by Tasleemat

Draft 2020-12 JSON Schema

Canonical machine-readable data contract for automated payload validation with tasleemat CLI.
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://tasleemat.pmo/schemas/completed/PMO-05.09.schema.json",
  "title": "Completed Prompt Library Log Data Contract",
  "description": "Additive structural schema validating completed Prompt Library Log artifact data payloads (PMO-05.09).",
  "type": "object",
  "properties": {
    "artifact_id": {
      "type": "string",
      "const": "PMO-05.09"
    },
    "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"
      ]
    },
    "prompt_library": {
      "type": "object",
      "properties": {
        "prompt_id": {
          "type": "string",
          "minLength": 1,
          "description": "A short identifier, so a prompt can be referred to in a meeting without its text being read out. A number is enough if it is the only one in use."
        },
        "use_case": {
          "type": "string",
          "minLength": 1,
          "description": "What the prompt is for, in one line: the task it was written to do and the situation it was written in. A prompt filed without its use case cannot be told apart from another one that reads almost the same."
        },
        "prompt_text": {
          "type": "string",
          "minLength": 1,
          "description": "The prompt as it is actually sent, not a description of it. What is filed here has to be usable by pasting it, because a paraphrase is a different prompt and will behave differently."
        },
        "expected_output": {
          "type": "string",
          "minLength": 1,
          "description": "What a good answer looks like, specifically enough to be checked. This is the column that makes the library auditable: without it there is nothing to compare a later response against."
        },
        "status_version": {
          "type": "string",
          "minLength": 1,
          "description": "Where the prompt stands, and which version this is. A prompt that has been revised without the version moving leaves every earlier result attached to a text that no longer exists."
        }
      },
      "required": [
        "prompt_id",
        "use_case",
        "prompt_text",
        "expected_output",
        "status_version"
      ]
    }
  },
  "required": [
    "artifact_id",
    "metadata",
    "prompt_library"
  ]
}
📋 Form Field Definitions Dictionary (Legacy Specification)
{
  "form_name": "Prompt Library Log",
  "document_reference": "PMO-05.09",
  "_llm_instructions": "Populate the fields of 'Prompt Library Log' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-05.09.",
  "fields": {
    "f01_Prompt_ID": {
      "section": "Prompt Library",
      "label": "Prompt ID",
      "guidance": "A short identifier, so a prompt can be referred to in a meeting without its text being read out. A number is enough if it is the only one in use.",
      "value": ""
    },
    "f02_Use_Case": {
      "section": "Prompt Library",
      "label": "Use Case",
      "guidance": "What the prompt is for, in one line: the task it was written to do and the situation it was written in. A prompt filed without its use case cannot be told apart from another one that reads almost the same.",
      "value": ""
    },
    "f03_Prompt_Text": {
      "section": "Prompt Library",
      "label": "Prompt Text",
      "guidance": "The prompt as it is actually sent, not a description of it. What is filed here has to be usable by pasting it, because a paraphrase is a different prompt and will behave differently.",
      "value": ""
    },
    "f04_Expected_Output": {
      "section": "Prompt Library",
      "label": "Expected Output",
      "guidance": "What a good answer looks like, specifically enough to be checked. This is the column that makes the library auditable: without it there is nothing to compare a later response against.",
      "value": ""
    },
    "f05_Status_Version": {
      "section": "Prompt Library",
      "label": "Status/Version",
      "guidance": "Where the prompt stands, and which version this is. A prompt that has been revised without the version moving leaves every earlier result attached to a text that no longer exists.",
      "value": ""
    }
  }
}