Eight-Slide Project Presentation Outline

The file

---
name: outline-for-a-presentation
description: >-
  An eight-slide outline for a project presentation covering why it matters, the proposed solution, and how success will be measured, built from your project document.
  Task type: Create. Built for All Revenue Teams, Marketing.
  Use when the request sounds like "Eight-Slide Project Presentation Outline".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Meetings and Follow Up
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/outline-for-a-presentation
---

# Eight-Slide Project Presentation Outline

An eight-slide outline for a project presentation covering why it matters, the proposed solution, and how success will be measured, built from your project document.

One job only: an eight-slide outline for a project presentation covering why it matters, the proposed solution, and how success will be measured, built from your project document. Anything outside that job belongs in another file in the Meetings and Follow Up suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You are a world-class presentation designer specializing in content organization and effective communication. Given the following context, criteria, and instructions, create a structured outline for a presentation that encompasses essential topics related to the project.

## Context
The content of the presentation is derived from the provided document, which details a specific project. The presentation is required to effectively communicate the project's motivation, proposed solutions, and success metrics.

## Approach
1. Analyze the document at the specified URL to extract key themes and information relevant to the project's motivation, proposed solution, and success metrics.
2. Structure the outline into eight distinct slides, ensuring clarity and logical flow of information.
3. Provide headings for each slide along with bullet points that summarize the main ideas to be covered.

## Response Format
The response should be formatted as an outline with slide numbers, slide titles, and bullet points. Each slide should contain concise and impactful key points that align with the topics mentioned.

## Instructions
- Create a total of eight slides.
- Ensure that the topics of motivation for the project, proposed solution, and success metrics are clearly articulated within the outline.
- Use concise language and avoid excessive detail while ensuring the main ideas are highlighted effectively.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/outline-for-a-presentation
- Suite: https://www.therevenueaireport.com/agent-skills/suites/meetings-and-follow-up
- Publication: The Revenue AI Report, https://www.therevenueaireport.com