[Slack channel], with your own.
Before you start, configure the Cortex MCP in the tool you’ll build with.
When something breaks
Every minute a responder spends looking up the owner and the last deploy adds to MTTR. Teams downstream of a breaking change usually find out when their own service fails.Triage agent
Runs on every alert or ticket. Finds the owning team, repo, and recent deploys before anyone is paged, and posts them where responders will see them.Prompt
Blast-radius checker
Runs on every pull request (PR). Lists the services that depend on the one being changed, and who owns them, right on the PR.Prompt
Keep ownership updated
An unowned service has no one to page when it breaks. These agents keep ownership current through every reorg.Orphan hunter
Runs weekly. Finds services with no owner and opens a ticket for each one.Prompt
Ownership sync
Runs nightly. Keeps Jira components, cloud tags, or routing tables in step with ownership in Cortex.Prompt
Standards and reviews
Skip building the review report by hand, and get failing checks chased between reviews instead of rehashed at them.Ops review prepper
Runs before each review. Turns Scorecard results into a status report, so nobody builds it by hand.Prompt
Fix chaser
Runs daily. Matches failing checks to the PRs fixing them and nudges the owners of everything else.Prompt
Migrations and audits
Replace the status spreadsheet and the rounds of Slack pings with an answer pulled from every service in Cortex, current whenever leadership asks.Catalog auditor
Runs on demand. Asks every service in the catalog the same question and returns a table.Prompt
Migration tracker
Runs weekly during a migration. Tracks which services have moved and posts progress by team.Prompt
Security
Each team running the vulnerable package gets a ticket the day the CVE drops, and scanner findings go straight to their owners.Finding router
Runs after each scan. Files every scanner finding with the team that owns the asset.Prompt
CVE scoper
Runs when a new Common Vulnerabilities and Exposures (CVE) entry is published. Finds every affected service and opens a ticket with each owning team.Prompt
Answers in chat
“Who-owns-this” questions stop landing on the platform team, and new hires get a map of their services on day one.Help bot
Always on in chat. Answers questions like who owns a service and how it deploys, using data from the catalog.Prompt
Onboarding guide
Runs for each new hire. Sends a new engineer a tour of the services their team owns.Prompt