# Theme clustering

A reusable skill the "Weekly support-ticket synthesis for product" recipe pulls in. Add it once and every agent on the team can use it.

Group raw tickets into root-cause themes instead of relying on surface-level tags.

## Method
1. Pull every ticket opened or closed in the support tools since the last digest.
2. Read each ticket's actual content, not just its assigned tag.
3. Group tickets by the underlying root cause they describe.
4. Merge tickets that use different tags but describe the same root issue.
5. Split a tag that actually covers two distinct root causes into separate themes.
6. Count tickets per theme and select 2-3 representative examples.

## Rules
- Cluster by root cause, never by the ticket's existing tag alone.
- A theme needs a minimum ticket count of (set on first run, then stored in memory) to be reported.
- Keep the theme taxonomy in memory and refine it as new patterns emerge, don't restart it weekly.
- Prefer a specific root-cause label over a vague catch-all theme name.

## Output
A list of themes, each with a ticket count and 2-3 representative ticket links.