CedarCopilot/cedar-mail

---
name: bug-triage-from-calls
description: Triage bugs from customer call transcripts. Extract issues from Cedar's POV, split into Isabelle vs Jesse lists, and send to #customer-success via webhook. Use when triaging bugs from customer calls, support conversations, or meeting transcripts.
---

# Bug Triage from Customer Calls

When given a transcript of Cedar talking to customers, extract bugs, issues, feature requests, and overall thoughts and route them to the right owners.

## Step 1: Analyze Transcript

Look at the transcript **from Cedar's POV**. Capture bugs, broken flows, friction, feature requests, and overall thoughts from the call. Be selective—don't over-list—but include both issues and ideas.

## Step 2: Create Two Lists

Split findings into two lists by owner:

**Isabelle** – Agent, backend, infrastructure, data (Gong sync, Salesforce, CRM fields, API/sync issues)

**Jesse** – Frontend, workflow, UI, navigation, shortcuts, views, email client

Each item: one clear, actionable bullet. Include brief context when it helps.

Also include a third section **Laundry List** for any action items that came up on the call that need to get done — e.g. sending a Stripe link, booking a follow-up, sharing a resource, following up with someone. These are tasks for Isabelle to action directly, not bugs.

## Step 3: Create Linear Tickets

Create one Linear issue per owner. Title format: `[{date}] {Customer name} check-in` (e.g. `[Mar 27, 2026] Acme check-in`).

**Isabelle's ticket:**
- Project: `Isabelle backlog` (id: `608e22cd-e7b0-4f8c-96d3-3d8404b6b287`)
- Team: `Cedar Mail`
- Status: `Todo`
- Label: `Customer` (id: `c7e39beb-7ace-43b9-8bfe-8eb0a1af4760`)
- Description: checklist of Isabelle's issues + the Laundry List items, each as `- [ ] item`

**Jesse's ticket:**
- Project: `Jesse` (id: `8ab4e224-15bc-4acc-89ba-515629860b4f`)
- Team: `Cedar Mail`
- Status: `Todo`
- Description: checklist of Jesse's issues, each as `- [ ] item`

Use the `Linear-save_issue` tool to create both tickets. Capture the returned issue `url` fields — you'll need them in the next step.

## Step 4: Send to Slack with Ticket Links

**Do not create a doc file. Do not open a PR.** Pipe the markdown directly into the script, appending a `## Tickets` section with the two Linear links:

```bash
cat <<'EOF' | pnpm run send-slack-triage
{customer name} – {date}

## Isabelle
- item 1
- item 2

## Jesse
- item 1

## Laundry List
- item 1

## Tickets
- Isabelle: {isabelle_ticket_url}
- Jesse: {jesse_ticket_url}
EOF
```

This posts all sections (including the ticket links) to #customer-success via the webhook.