Prompt Pattern Library by Use Case

Each pattern below is a starter template. Copy the block into your AI tool, fill in the bracketed fields, and adapt the specifics to your actual task. Patterns are optimised for general-purpose language models (Claude, GPT-4-class); results will vary by model and version. Treat all outputs as drafts requiring human review.

How to Use This Library

A good prompt has four components: role, context, task, and format. The patterns below include all four. When adapting a pattern, keep all four components and replace only the bracketed specifics.

1. Summarisation

1.1 Long document summary

```

You are an analyst preparing a briefing for a senior executive who has 5 minutes to read it.

The document below is [describe document: e.g. a vendor contract, a research paper, a board report].

Summarise it in the following format:

• One-sentence overall summary
• Three to five key points, each in one sentence
• Any decisions or actions required, as a numbered list
• Any significant risks or concerns, flagged clearly

Do not include background that is obvious to the executive. Do not pad the summary.

[Paste document text here]

```

1.2 Meeting notes to action items

```

You are an executive assistant. Convert the meeting notes below into a structured action-item list.

For each action item, extract:

• Owner (the name in the notes responsible for the action)
• Action (one sentence describing what needs to be done)
• Due date (exact date if mentioned; "TBD" if not)

Group action items by owner. If an item has no clear owner, flag it with "Owner unclear."

[Paste meeting notes here]

```

2. Code Review

2.1 Code review request

```

You are a senior software engineer with expertise in [language/framework]. Review the code below.

For each issue you identify, state:

1. File and line number (or describe the location)
2. Issue type: bug, security vulnerability, performance concern, readability, or style
3. Severity: critical, high, medium, or low
4. Specific recommendation

Do not suggest changes that are purely stylistic if the code is otherwise correct. Focus on issues that matter.

[Paste code here]

```

2.2 Explain unfamiliar code

```

You are explaining code to a competent engineer who is unfamiliar with [language/framework/codebase].

Explain what the code below does, in plain language. Structure your response as:

1. What this code does overall (two to three sentences)
2. How it works — walk through the logic step by step
3. Any non-obvious dependencies, side effects, or gotchas

Do not explain language basics the engineer would already know.

[Paste code here]

```

3. Document Drafting

3.1 First-draft business document

```

You are a business writer drafting a [document type: e.g. policy, proposal, memo] for [audience: e.g. the security team, external vendors, the board].

Draft the document based on the following input:

• Purpose: [one sentence]
• Key points to cover: [bullet list]
• Tone: [formal / semi-formal / direct]
• Length: approximately [X] words

Use plain language. Avoid jargon unless the audience would expect it. Leave [PLACEHOLDER] where you need input I have not provided.

```

3.2 Edit for clarity

```

You are an editor. Improve the clarity and conciseness of the text below.

Rules:

• Do not change the meaning or omit any substantive information
• Cut unnecessary words and passive voice
• Break up sentences longer than 30 words
• Flag any statements that are ambiguous or that you are unsure about rather than guessing

Provide the edited text followed by a short list of the main changes you made.

[Paste text here]

```

4. Research and Analysis

4.1 Structured research briefing

```

You are a research analyst. Using only the information I provide below, answer the research question.

Research question: [Question]

Rules:

• Do not use knowledge outside the provided text
• If the provided text does not contain enough information to answer the question, say so explicitly
• Cite the specific passage from the provided text that supports each point you make
• Flag any conflicting information across the provided texts

[Paste source text(s) here]

```

4.2 Identify counterarguments

```

You are a critical reviewer. I will provide a position or proposal. Your job is to identify the strongest counterarguments.

For each counterargument:

1. State the counterargument clearly
2. Rate its strength: strong, moderate, or weak
3. Suggest how the original position could be strengthened in response

Do not advocate for the counterarguments. Your role is to prepare me to respond to them.

Position or proposal: [Text here]

```

5. Customer Communication

5.1 Draft a customer-facing response

```

You are a customer success professional at [Company]. Draft a response to the customer message below.

Tone: professional, direct, and empathetic — not apologetic to the point of being unconvincing.

Requirements:

• Acknowledge the customer's concern in the first sentence
• Provide a clear answer or next step
• If you cannot resolve the issue in this message, state what will happen next and by when
• Do not make commitments I have not confirmed: leave [CONFIRM WITH TEAM] where you would need to check something

Customer message: [Paste message here]

Context (optional): [Any relevant account or issue context]

```

5.2 Simplify technical content for customers

```

You are translating a technical explanation into language appropriate for a business user with no technical background.

The original text is: [Paste technical text here]

The customer's concern is: [Describe what they want to understand]

Write the explanation at approximately a 10th-grade reading level. Use an analogy if it helps. Do not talk down to the customer. Keep it under 150 words.

```

6. Planning

6.1 Project plan outline

```

You are a project manager. Based on the information below, create a structured project outline.

Project: [Name and one-sentence description]

Goal: [What does success look like?]

Constraints: [Timeline, budget, team size, known dependencies]

Provide:

1. A phased work breakdown with estimated effort per phase
2. Key milestones with suggested dates (relative, e.g. "Week 3")
3. Risks and assumptions — at least three of each
4. Open questions that need to be resolved before work starts

Flag any places where you are making assumptions due to missing information.

```

6.2 Decision analysis

```

You are an advisor helping me make a structured decision.

Decision: [Describe the decision to be made]

Options under consideration: [List the options]

Constraints and priorities: [e.g. cost, speed, reversibility, team capacity]

For each option provide:

• Pros (concrete, not generic)
• Cons (concrete, not generic)
• Risk profile (what could go wrong, and how bad would it be)
• My best guess at your recommendation and why

End with a clear recommendation and the single most important factor driving it.

```