build-presentation

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: build-presentation
description: "Orchestrator for the installed presentation skill suite. Use when the user wants a guided end-to-end presentation workflow."
---

# Build Presentation (Orchestrator)

Coordinates the full presentation pipeline. Detects what has already been done and guides the user to the next step.

## Installation boundary

This skill orchestrates `discover-presentation`, `structure-agenda`, `generate-slides`, `generate-images`, `generate-diagrams`, and `proofread-presentation`; it does not contain those capabilities itself. Install it together with that suite. The phase skills remain separately useful for focused work in an existing project folder.

## Gotchas
- Advance phases only when the current exit criteria are fully satisfied.
- Require structure to be complete before calling `generate-slides`. Process requests sequentially; always build the agenda first.

## Startup

Before proceeding:
1. Confirm the project folder is readable.
2. If it already exists, require `PROJECT.json` to identify a Presentation Project.
3. From the project folder, run `git rev-parse --is-inside-work-tree`. If it
   succeeds, enable Git checkpoints for this run. If it fails, tell the user
   before making presentation changes that they will not be able to revisit
   persisted states from the development cycle, then continue without commits.

Each invoked phase owns the preflight for the external tools it actually uses.

## Git checkpoints

When Git checkpoints are enabled, snapshot the project folder's Git status
before invoking a phase. After a phase completes, inspect the status again.
If that phase changed presentation files, stage only the files it changed and
create one commit before offering or invoking the next phase. Use a message
that names the completed phase, for example:

```
presentation: complete discovery
presentation: complete agenda structure
presentation: complete slide generation
presentation: complete image generation
presentation: complete diagram generation
presentation: complete proofreading
```

Never stage pre-existing, unrelated, or secret-bearing changes. A phase that
makes no changes creates no commit. If Git cannot create a checkpoint, report
the exact failure and do not advance to a later phase until the user has chosen
how to proceed without that persisted state.

When a rewrite sends the project back to an earlier phase, finish the restart
guard and commit its confirmed file changes before re-invoking that phase. Make
the reset evident in the message, for example:

```
presentation: reset to agenda structure — revise narrative
```

Then checkpoint the re-run phase on completion, as usual. In a non-Git project,
repeat the persistence limitation whenever a restart is confirmed.

## State detection

Read `PROJECT.json` and the named project artifacts directly. Require
`projectType: "presentation"` whenever state exists:

| State | Condition |
|-------|-----------|
| Nothing started | `PROJECT.json` missing |
| Discovery done | `PROJECT.json` exists, `phases.discovery.status == "done"` |
| Structure done | `AGENDA.md` exists, `phases.structure.status == "done"` |
| Generation done | `PRESENTASJON.md`, `PRESENTASJON.html`, and `PRESENTASJON.pdf` exist, `phases.generation.status == "done"` |
| Media done | Media specs exist and corresponding `phases.images.status` and/or `phases.diagrams.status` are "done" or "skipped" |
| Proofread done | `phases.proofread.status == "done"` |

## User guidance (based on state)

### Nothing started
> "This looks like a new project. Would you like to start by gathering requirements? (discover-presentation)"

→ Call `discover-presentation`, then continue.

Before advancing to structure-agenda, verify [exit criteria](EXIT_CRITERIA.md#discovery-exit-criteria).

### Discovery done, no agenda
> "Discovery is complete. Would you like to build the agenda now? (structure-agenda)"

Options:
- **Yes** — call `structure-agenda`
- **Redo discovery** — call `discover-presen