Back to the Playbook
OperateOP-05
Review incident
Link an incident to the commits, pull requests and owners that likely caused it, and turn the resolution into a postmortem, a runbook and reliability work.
Product statusAvailable now
Context in4 required inputsIncident report and timeline · Recent commits and pull requests · Affected components
TransformationEngineer + Engineering Agent + Architecture AgentCode Analysis · Find Code Owners · Atlassian · Local Files
OutcomeIncident analysis with suspected cause, postmortem draft, runbook and backlog proposals.Artifact: Postmortem
Owner
Engineer
Human + Agent
Participants · Agents
Product ManagerQAEngineering AgentArchitecture Agent
Trigger
An incident is resolved, or recurring incidents share a pattern.
Required context
JiraIncident report and timelineCodeRecent commits and pull requestsArchitectureAffected componentsJiraRelated bugs
Optional context
FilesLogs and monitoring dataJiraPrevious incidentsCustomer evidenceCustomer impact
Skills
Code AnalysisFind Code OwnersAtlassianLocal Files
Methods used inside this Activity: Blameless postmortem · Incident clustering by symptom, component and root cause
Activity steps
- 1Link the incident to suspect commits, pull requests and owners.
- 2Cluster with previous incidents by symptom, component and root cause.
- 3Draft the postmortem and the runbook.
- 4Propose reliability work for the backlog.
Output
Incident analysis with suspected cause, postmortem draft, runbook and backlog proposals.
Artifacts
Creates: Postmortem, Runbook
Updates: Jira bug
What good looks like
- The cause is linked to code, not guessed.
- Blameless.
- Patterns across incidents are named.
- Every action has an owner.
Quality gate
The engineering lead approves the postmortem and the reliability work.
Destination
ConfluenceJiraProduct Brain
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Deep dives from the AI PM Lab
Articles that explain the thinking behind this Activity.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.