pitch-deck-builder

Files (1)

• SKILL.md

SKILL.md (first lines)

# Pitch Deck Builder

Use this skill to produce an editable, shareable PPTX built with `pptxgenjs`.
The deck should have a clear narrative structure, self-contained slides, cited
figures, a verified glossary, and appendix slides for supporting detail.

Default source of truth for content is Notion when available. Keep repo-local
or workspace-local source material canonical if the user names another source.

## Core Rule

Front-load decisions before writing or building slides. The phases below are
sequential. Do not advance past a gate until the human approves that phase.

## Phase 0: Clarify

Ask these five questions in a single message. Do not proceed until all are
answered.

1. Audience: who reads this, and what do they already know?
2. Ask: what should the reader do or feel? Split by persona if needed.
3. Tone register: neutral internal reference, warm pitch, or confident
   opportunity statement?
4. Format: editable PPTX, PDF, or both?
5. Source context: Notion pages, repo docs, files, or other material to draw
   from?

## Phase 1: Source Setup

If Notion is available and relevant:
- fetch the main project Notion page before writing
- create or update one child page named `Deck - Content & Structure`
- append confirmed slide copy as each slide is approved
- mark each approved slide with `confirmed`
- flag visual ideas as callouts or a clearly labeled visual-notes block

If Notion is unavailable:
- use the user's named files or repo docs as the source context
- keep a local outline artifact only when the deck work needs durable
  intermediate state

## Phase 2: Narrative Spine

Identify the conceptual backbone before writing slide titles. Everything else
must support or resolve the spine.

Common spine forms:
- six-point failure-and-resolution framework
- before/after comparison with numbered matched items
- three forces converging
- one company proved it, nobody productized it

Gate: get explicit approval before writing slide content.

## Phase 3: Slide Structure

Propose the structure as:

```text
# | Headline | What this slide does
```

Rules:
- headline states the conclusion, not the topic label
- every headline should be informative to a cold reader with no context
- keep the main deck concise; move support detail to appendix

Standard sequence:

```text
Cover -> Setup -> Blueprint/problem -> Structural insight -> Why tools fail ->
Product -> Why now -> Market + competitive proof -> Business model ->
Proof/traction -> Ask by persona -> Glossary -> Appendix
```

Gate: get the structure approved before writing content.

## Phase 4: Design Selection

Propose design options before building. Do not pick unilaterally unless the
human asks you to choose.

Named presets:

| Preset | Palette | Best for |
| --- | --- | --- |
| Dark Editorial | `1E1E1E` background, white text, `2563EB` accent | technical, premium |
| Clean Analytical | `FFFFFF` background, `0F1E3C` navy titles, `1B4FBA` blue | analytical pitch quality |
| Split | `0F1E3C` dark cover, `FFFFFF` content, `D97706` amber accents | mixed strategy/product decks |
| Restrained Editorial | `F7F6F2` off-white, `1C1C1C` charcoal cover, `3D5A80` slate blue, `C2692A` amber | distinctive but restrained |

Default font specs:
- titles: Georgia 22-24pt bold
- labels: Calibri 14pt bold
- blueprint numbers: Georgia 15-17pt accent
- body: Calibri 13pt minimum
- tables: 10.5-11pt minimum

## Phase 5: Write Slide By Slide

Recommended writing order:

```text
Blueprint pair -> Cover -> Setup -> Insight -> Product -> Rest -> Appendix
```

Gate on each slide before writing the next.

Mandatory content rules:

- Self-contained: every slide reads cleanly without adjacent slides.
- Concrete examples: every analytical slide includes at least one real example
  in muted italic text.
- Blueprint structure: the framework appears twice, once as problem and once as
  resolution, with identical numbering and labels.
- Generic versus vertical: main deck blueprints stay generic unless the deck is
  explicitly vertical-specific; appendix slides may instantiate vertical
  examples.
- Persona split: create one ask slide per reader type, such as buyer,

From armin-haghi/llm-os, MIT.

More from armin-haghi/llm-os