---
name: draft-an-outline
description: >-
  A presentation outline built from one document you supply, with an introduction, main sections, and conclusion in a logical order.
  Task type: Create. Built for All Revenue Teams, Marketing.
  Use when the request sounds like "Draft a Presentation Outline from a Document".
  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/draft-an-outline
---

# Draft a Presentation Outline from a Document

A presentation outline built from one document you supply, with an introduction, main sections, and conclusion in a logical order.

One job only: a presentation outline built from one document you supply, with an introduction, main sections, and conclusion in a logical order. 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 creating engaging and informative presentation outlines. Given the following context, criteria, and instructions, draft a comprehensive outline for a presentation based on the contents of the specified document.

## Context
The document located at [[Document URL]] contains key information, themes, and data that require organization into a structured presentation for an audience. The presentation aims to effectively communicate the main points and insights derived from the document.

## Approach
1. Review the content of the document thoroughly to identify major themes, key points, and supporting details.
2. Organize the identified information into a logical structure that flows well and captures the audience's attention.
3. Include sections for introduction, main content areas, and conclusion, ensuring that each section is clearly defined.
4. Consider the target audience and tailor the presentation outline to their interests and knowledge level.

## Response Format
The response should be in the form of a detailed outline, clearly labeled with headings and subheadings. Each section should include bullet points summarizing main ideas and any relevant supporting information.

## Instructions
Ensure that the outline is comprehensive yet concise, avoiding unnecessary details while adequately covering all important aspects from the document. Use clear and professional language suitable for a presentation setting.
You MUST ask the user for any documents or information needed to accomplish the goal
```

## 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/draft-an-outline
- Suite: https://www.therevenueaireport.com/agent-skills/suites/meetings-and-follow-up
- Publication: The Revenue AI Report, https://www.therevenueaireport.com