✨ Multi-meeting Type Support - Multi-meeting support to detect meeting type and select dashboard template/skills

[suiyangqiu]

Cc: @suiyangqiu @calumjs @joshbermanssw @yaqi-lyu @eddie @louis
Hi Team!

🟥 Watch the video (1 min 24 sec)

Pain

Tiger currently assumes an incoming meeting is a Sprint Review and immediately runs the Sprint Review dashboard template/skills/analyzers. This blocks generalising Tiger to support multiple meeting types (e.g. different dashboards and analyzers) while still keeping a single ingestion path via the existing webhook.

Acceptance Criteria

1. Tiger can route a newly received meeting to the correct “meeting type” processing pipeline (dashboard template + analyzers) without changing the webhook entry point.
2. A meeting type can be explicitly set via a CLI flag.
3. If no CLI flag is provided, Tiger attempts to infer the meeting type from meeting context using AI and selects the appropriate meeting type.
4. Meeting type selection drives which Tiger “skills” (or equivalent configuration) are used to run the relevant analyzers and templates.
5. Adding a new meeting type requires only adding a new skill/template configuration (no changes to the webhook contract).

Screenshot

Thanks!

[suiyangqiu]

Heads up to anyone watching the video of the YakShave, apologies for the disturbance in the middle of the recording, I had a process running on the side and Peon Ping triggered 😅