Processes/product — standing up the product stackproduct
On-call & incidents — product processOn-call & incidents
Set up PagerDuty with on-call schedules, escalation policies, incident workflows, and post-mortem process.
PagerDuty API fully supports schedules, escalation policies, and service configuration.
Current agent ceiling
An agent can run 6 of 6 steps — 6 of them behind a human approval gate ⏸
No gaps — every step of this process is agent-runnable today.
How it runs
Route-coded block flow: emerald = agent, amber = manual form/portal, red = needs a human. ⏸ approval gate · ⏳ async wait.
runs in parallel · 2
Honeycomb
Grafana05Set up Slack incident channel
agent1 API call
- conversations.create
06Create post-mortem template
agent
Notion59⏸ approval gateor:
Linear56·
monday.com52
1 API call
- POST /v1/pages
Context the agent needs first: engineering team · on-call rotation preferences (from the founder)
The market options
Each role resolves against its arena’s live leaderboard — the default is the process’s canonical vendor, alternatives ranked by agent-readiness.
PagerDutydefault57/100 agent-ready
incident.io49/100 agent-ready
Rootly39/100 agent-ready
FireHydrant35/100 agent-ready
Better Stack29/100 agent-ready
- Notiondefault59/100 agent-ready
- Linear56/100 agent-ready
- monday.com52/100 agent-ready
Asana45/100 agent-ready
ClickUp35/100 agent-ready
Jira24/100 agent-ready
Slackdefault65/100 agent-ready
Discord59/100 agent-ready
Zulip34/100 agent-ready
Microsoft Teams32/100 agent-ready
Buzz28/100 agent-ready