Choose the task you need to complete. Driver can trace the relevant code, compare the supplied evidence, and prepare a reply or handoff. Your team runs tests, confirms deployment, and copies reviewed results into Jira or customer conversations.
| Task | Guides |
|---|---|
| Work a ticket across support and engineering | Working a ticket together |
| Assess a customer report and prepare an escalation | Support |
| Review ticket performance | Support lead |
| Investigate an escalation, check production evidence, and report fix availability | Engineering and SRE |
| Compare options, assess impact, and explain releases | Product managers |
| Plan regression checks and verify reported behavior | QA |
| Understand dependencies and record a decision | Architects and tech leads |
| Learn an unfamiliar system | New engineers |
| Prepare for a customer call | Customer success |
For a concrete example, follow a webhook ticket from first report to verified fix.
Each task names its required inputs. Supply relevant log excerpts, deployment records, or configuration values when a question depends on what happened in an environment. Source comparisons use accessible branches or a supplied diff; prepared maps and history require Advanced Codebase Context.