| name | oncall-handoff |
| description | Generate a comprehensive on-call handoff document by aggregating open incidents, ongoing issues, recent deployments, and systems to watch. Orchestrates PagerDuty, Jira, and ArgoCD agents. Use during on-call rotation changes or shift handoffs. |
On-Call Handoff
Build a structured handoff document for the incoming on-call engineer by collecting data from PagerDuty, Jira, and ArgoCD.
Instructions
Phase 1: Current Incident State (PagerDuty Agent)
- Active incidents - all triggered and acknowledged incidents
- Recently resolved incidents - resolved in the last 24 hours (may recur)
- Current on-call schedule - who is on-call now, who is taking over
- Upcoming maintenance windows - scheduled within the next 48 hours
Phase 2: Ongoing Issues (Jira Agent)
- Open incident tickets - Jira issues labeled `incident`, `outage`, `p0`, `p1`
- Known issues - issues labeled `known-issue` or `workaround`
- Recently closed issues - resolved in last 48 hours that may have follow-ups
- Pending changes - tickets in "Ready for Deploy" or "In Review" status
Phase 3: Environment State (ArgoCD Agent)
- Recent deployments - applications synced in the last 48 hours
- Unhealthy applications - any OutOfSync, Degraded, or Unknown apps
- Pending syncs - applications with pending changes not yet deployed
- Recent rollbacks - any applications that were rolled back
Phase 4: Compile Handoff Document
Organize all data into a structured, scannable document with clear action items.
Output Format
```markdown
