td-deck

Files (3)

• SKILL.md
• README.md · samples/
• specific_instructions.md

SKILL.md (first lines)

# TD Deck Skill

## On activation

**Always announce that this skill has been triggered.** At the very start of your first reply, output exactly one line:

> **TD Deck skill activated.** I'll build a presentation deck from your TD document for the IP review board and technical reviewers.

Then proceed immediately to Phase 1. No further preamble.

---

## Prerequisites

- **Required:** `python-pptx` (`pip install python-pptx`). All `.pptx` generation depends on it.
- **Optional:** LibreOffice (`soffice`) and poppler (`pdftoppm`) — enable the render check in Phase 4. LibreOffice + Pillow + network access also enable icons on the big-type slides via `../icon_to_png.py`. If anything is missing, that step is skipped, never installed unprompted.

---

## Required reading

**`../deck-style.md`** — copy rules, visual bans, default visual system and quality gate. Shared with `pitch-deck`. Read it before Phase 2; every rule applies to this skill, with one precedence rule: when `template.pptx` is used, the template's own styling wins and the visual bans apply only to shapes you add. The copy rules always apply.

---

## What this produces

A single `.pptx` presentation deck per request, derived entirely from the content of a completed TD document. The deck is saved in the td-deck output directory — not alongside the TD file.

**This skill does not write or edit TD documents.** If the TD is not yet complete, stop and tell the user to finish it first (using the `td` skill), then come back.

---

## Bootstrap — first-time setup check

Run this before anything else, every invocation:

1. Check whether `docs/td-decks/` exists at the project root.
2. **If it does not exist**, create it:
   ```bash
   mkdir -p docs/td-decks/samples/
   ```
   Then tell the user:
   > "This skill requires `docs/td-decks/` in your project root — created it now along with `docs/td-decks/samples/`. Before I proceed, consider adding:
   > - `docs/td-decks/samples/template.pptx` — your organization's PowerPoint template (the deck will be built from it)
   > - Any reference TD presentation decks (`.pptx`) alongside it — for additional visual calibration
   >
   > These are optional. Tell me to proceed now and I'll fall back to a default structure."

   Wait for the user's response before continuing to Phase 1.

3. **If it exists** but `docs/td-decks/samples/` does not, create it silently and proceed.

---

## Samples handling

The `docs/td-decks/samples/` directory serves two purposes:

1. **`template.pptx`** (optional) — if present, used as the base for all deck generation. All slides, layouts, and styles are inherited from it.
2. **Reference decks** (optional) — any other `.pptx` files, used for visual and structural calibration. Do not borrow content from them.

**On startup, always check `docs/td-decks/samples/` for both.** Specifically:

- Look for `docs/td-decks/samples/template.pptx` — the template file. If found, load it via `Presentation('docs/td-decks/samples/template.pptx')` and **inspect its structure before generating anything**: read every slide's title placeholder and content placeholders, note instructional/guidance text already in placeholders (this is template scaffolding — it must be replaced with real content, not appended to), note slide count limits per section, and identify slides that cannot be filled from the TD alone (see Phase 2).
- Look for any other `.pptx` files in `docs/td-decks/samples/` — read them for style cues.
- If `docs/td-decks/samples/README.md` exists, read it — it may document house-convention notes or deviations. These override what you'd infer from the files alone.

**If `docs/td-decks/samples/` is empty**: note the absence of both template and style references, but do not stop — continue to Phase 1. Both absences will be flagged in the hand-off summary.

---

## Output directory

Always use `docs/td-decks/` for output and `docs/td-decks/samples/` for reference samples. These paths are fixed — do not look for or create alternative locations.

Output filename pattern: `<PROJECT>_TD_<same-slug-as-source-TD>_deck_<YYYY-MM-DD>.pptx`

Where `<PROJECT>` and `<same-slug-as-source-TD>` are derived from the source TD filename. Keep the slug consistent so the deck and its source TD are obviously paired.

---

## Workflow

### Phase 1 — Pre-flight

#### 1a. Validate the TD file

The argument-hint should have provided the path. Resolve it:

- If the file exists and is readable: proceed.
- If the file does not exist: stop immediately.
  > "I can't find a TD file at `<path>`. Please check the path and re-invoke. The TD must be a completed `.md` file generated by the `td` skill."
- If no path was provided via the argument-hint: ask the user for it before doing anything else.

Read the TD file end-to-end. Build an internal map of its sections before proceeding — you'll use this in Phase 2.

#### 1b. Template and style check

Already handled by "Samples handling" above. At this point you know:

- Whether `docs/td-decks/samples/template.pptx` exists → will use it as the generation base, or fall back
- Whether reference style decks exist → will use them for visual calibration, or proceed without

**If no `template.pptx` was found**: tell the user and offer two options (via **AskUserQuestion** when available):

> "No `template.pptx` found in `docs/td-decks/samples/`. How would you like to proceed?
> (a) Use a default TD presentation structure I'll propose — a standard layout for IP review board presentations, which you can adjust.
> (b) Describe the outline yourself, slide by slide, and I'll build exactly what you specify."
>
> To use your own template in future runs, drop it into `docs/td-decks/samples/template.pptx`.

If the user picks **(a)**: proceed with the default structure defined in "Default outline" below. Confirm the proposed outline with the user before generating.

If the user picks **(b)**: collect the slide-by-slide description from the user. Confirm it back before generating.

#### 1c. Ask any remaining questions

Bundle these and ask once:

From cslev/skillet, MIT.

More from cslev/skillet