## Summary The internal MVC of the GitLab Duo Slack Integration (https://gitlab.com/gitlab-org/gitlab/-/work_items/590434) validated that engaging with Duo from Slack removes meaningful toil (thread → issue, codebase/issue search, triggering agent flows) and shipped the core infrastructure: messaging adapter, app_mention handling, OAuth scopes & manifest, and initial user documentation. This epic tracks the work to take that internally validated capability and roll it out to customers as a supported, self-serve feature. ## Problem Customers work primarily in Slack and repeatedly context-switch into GitLab for common tasks (creating issues from discussions, checking what's already known, kicking off work). Multiple Ultimate/DAP customers have requested this capability through CSM/SA channels, and it has surfaced as a factor in active opportunities. The building blocks exist from the internal MVC, but they were built and validated for our own dogfooding. They now need to be made safe, self-serve, and supportable for external tenants. ## Desired outcome An easy way to engage with Duo through Slack for common use-cases. ## Related - Internal MVC (infrastructure, scopes, docs): #590434 - Related: #588096