Investigate a slowdown after a release
After a release makes a page slower, the bot goes through dashboards and traces, names the most likely hotspot and writes a short report that separates facts from guesses.
Steps
- Connect observability and analytics tools with read access
- Describe the symptom and when it started
- Ask for a write-up with links and screenshots; no setting changes
Starter prompt
Checkout has been slower since yesterday's release. Look through our dashboards and traces, find the most likely cause and write a short report with links and screenshots. Keep facts and hypotheses apart. Don't change alerts or settings.
Guardrail: Read-only access is enough; production changes stay with engineers.
Prompts are our own examples. Results from sources are as reported by their authors.