Generate workshop slides and notes
workshop-generateworkflowsetup L3★16
edwinhu/workflows ↗What it does
Generate slide and notes from Slide Spec by section
Best for
Generating workshop slides in phases: per-SECTION fan-out enforces intra-section flow and composability; assembly gate catches compile errors before marking success.
Inputs
- · [object Object]
Outputs
- · [object Object]
- · [object Object]
Requires
- · OUTLINE.md (Slide Spec table reader)
- · SOURCES.md (inventory reference)
- · Paper PDF (if linked)
- · typst compiler (for slides.typ + notes.typ)
Preconditions
- · OUTLINE.md has Slide Spec table with columns: Slide | Section | Takeaway | Bullets | Inventory | Visual | Notes
- · One agent per SECTION (parallel) — each writes fragment files (slides fragment + notes fragment)
- · Section fragments written to .planning/slide-fragments/
- · Assembly agent concatenates section fragments in order into slides.typ + notes.typ
- · Typst compiler invoked on assembled output
Failure modes
- · Slide Spec table missing from OUTLINE.md → outlineReadable=false, abort
- · Inventory ID cited but not in SOURCES.md allowed list → agent limited to allowed ids
- · Section fragment write fails → status=error for that section, continues
- · Typst compile error → compileError captured, slidesPdf path null
- · Missing SOURCES.md or paper path → sourcing phase incomplete but section generation continues
Trust signals
- · Section is atomic unit (not per-slide), preserves flow
- · Each section agent cites only allowed inventory (schema-enforced)
- · Compiled PDF proves slides.typ + notes.typ are valid
- · Fragment files enable incremental regeneration (onlyChecks parameter)
- · Typst compiler is ground truth (no silent markup errors)