# Develop Agent for Automatic Triage of Corrective Action Issues ## Problem Statement When corrective action issues are created from incidents, they currently require manual triage. This creates delays in getting critical follow-up work to the appropriate teams and can result in important corrective actions being overlooked or delayed. ## Solution Develop an incident-automation service that handles corrective-action issues as they're created. **Work is being delivered in phases** to ship value iteratively rather than waiting for the full triage flow. ### Phase 1 — Enrichment and Triage The service reads the parent incident from incident.io and synthesizes a structured description on the corrective-action issue — originating incident context, impact, contributing cause, affected services, acceptance criteria. This lays the groundwork for Phase 2 by producing a structured `Primary service` field that makes service-to-team mapping a lookup rather than an inference. The same service then performs the triage flow on enriched issues: 1. **Service identification and team mapping** — primary source [Service Catalog](https://gitlab.com/gitlab-com/runbooks/-/blob/master/services/service-catalog.yml); fallback handbook search. 2. **Team assignment** — identify and assign the team manager via [Product Categories Handbook](https://about.gitlab.com/handbook/product/categories/) and [Features Categories Handbook](https://handbook.gitlab.com/handbook/product/categories/features/). ### Phase 2 — Further Improvements - Absorb further incident-management handlers (e.g., Woodhouse's artifact-linking) once Phase 1 ships. ## Completion Criteria - [x] Issue context is sufficient or additional information has been requested - [x] Service has been identified and mapped to team - [x] Team manager has been pinged and assigned - [ ] Add documentation and runbook around this automation *** _Description was generated using AI_