Team Prompt Library Worksheet

# Team Prompt Library Worksheet

**Team / department:** ___________________________
**Tool(s) this library applies to:** ___________________________
**Library owner:** ___________________________
**Last reviewed:** ___________________________

---

## About This Worksheet

A prompt library is a shared collection of AI prompts that your team has tested and found useful. This worksheet helps you:
- Capture prompts that work well for recurring tasks
- Document the context in which each prompt is most effective
- Share knowledge so colleagues don't have to reinvent the wheel
- Identify prompts that need improvement

---

## How to Add a Prompt

1. Fill in the table below with a description, the actual prompt text, and notes on usage.
2. Mark prompts as Tested / Draft / Needs improvement based on team feedback.
3. Review and update the library at least quarterly — prompts may need updating as tools change.
4. Share the library in your team's shared drive or collaboration tool.

---

## Prompt Entry Format

Copy the block below for each prompt you want to add.

---

**Prompt ID:** ___________
**Category:** (e.g. Drafting / Summarising / Research / Formatting / Code / Analysis)
**Task description:** (What is this prompt for, in plain language?)
___________________________

**Prompt text:**
*(Copy and paste exactly as used — use [SQUARE BRACKETS] for sections staff should replace)*

~~~
[Paste prompt here]
~~~

**Example of what to replace:**
- [TOPIC] → replace with the subject matter (e.g. "data protection training")
- [AUDIENCE] → replace with who the content is for (e.g. "non-technical staff")
- [LENGTH] → replace with your target length (e.g. "300 words")

**Tool tested on:** ___________________________
**Tested by:** ___________________________  **Date:** ___________________________
**Status:** Tested and effective / Draft — needs testing / Needs improvement
**Notes / known limitations:**
___________________________

---

## Starter Prompt Templates

Use these as a starting point and adapt for your team's needs.

---

**Prompt ID:** PL-001
**Category:** Drafting
**Task:** Write a formal email

~~~
Write a professional email on behalf of [NAME/ROLE] to [RECIPIENT] about [TOPIC].

Tone: formal / friendly-professional / urgent (delete as appropriate)
Length: approximately [NUMBER] words
Key points to include:
- [POINT 1]
- [POINT 2]
- [POINT 3]

End with a clear call to action: [WHAT YOU WANT THE RECIPIENT TO DO]
~~~

**Notes:** Remove the sender's name before pasting if using a shared AI account. Always review before sending.

---

**Prompt ID:** PL-002
**Category:** Summarising
**Task:** Summarise a long document

~~~
Summarise the following document in [NUMBER] bullet points suitable for [AUDIENCE, e.g. a senior manager who needs a 2-minute briefing].

Focus on:
- Key decisions or recommendations
- Actions required
- Risks or issues raised

[PASTE DOCUMENT TEXT HERE]
~~~

**Notes:** For documents with personal data, remove names and identifying details first.

---

**Prompt ID:** PL-003
**Category:** Drafting
**Task:** Create a meeting agenda

~~~
Create a [LENGTH, e.g. one-hour] meeting agenda for a [TYPE OF MEETING, e.g. project update meeting] with the following objectives:

1. [OBJECTIVE 1]
2. [OBJECTIVE 2]
3. [OBJECTIVE 3]

Attendees: [LIST ROLES, NOT NAMES]
Format: include time allocations and a named owner for each item.
~~~

---

**Prompt ID:** PL-004
**Category:** Analysis
**Task:** Compare options or approaches

~~~
Compare the following [NUMBER] options for [TASK OR DECISION]:

Option A: [DESCRIBE]
Option B: [DESCRIBE]
Option C: [DESCRIBE]

For each option, provide:
- Key advantages
- Key disadvantages
- Best suited for (what context or scenario)

Present the output as a table.
~~~

---

**Prompt ID:** PL-005
**Category:** Research
**Task:** Explain a concept in plain language

~~~
Explain [CONCEPT] in plain English suitable for [AUDIENCE, e.g. someone with no technical background].

Keep the explanation to [LENGTH, e.g. 150 words].
Avoid jargon. If technical terms are unavoidable, define them briefly.
Include a simple real-world example.
~~~

---

## Team Prompt Log

| Prompt ID | Category | Task description | Tool | Tested by | Date | Status |
|-----------|----------|-----------------|------|-----------|------|--------|
| PL-001 | Drafting | Formal email | | | | |
| PL-002 | Summarising | Summarise document | | | | |
| PL-003 | Drafting | Meeting agenda | | | | |
| PL-004 | Analysis | Compare options | | | | |
| PL-005 | Research | Plain English explanation | | | | |
| PL-006 | | | | | | |
| PL-007 | | | | | | |

---

## Prompts That Did NOT Work Well

Document prompts that consistently produce poor results so colleagues can avoid them or improve them.

| Description of task | Prompt tried | Why it didn't work | Suggested fix |
|--------------------|--------------|--------------------|---------------|
| | | | |
| | | | |

---

## Library Review Notes

| Review date | Reviewed by | Changes made |
|------------|-------------|-------------|
| | | |
| | | |