groups

DevOps War Room — Bot Team Template for Devops

Bot Team

· Updated Mar 23, 2026

Incident response team with log analysis and deployment management on Slack.

star 0 stars content_copy 1 deploys slack v1.0.0

Template DevOps War Room bundles a ready-to-deploy workspace for devops workflows. Install in one click from the Aerostack dashboard or via aerostack init --template=devops-war-room.

What does DevOps War Room do?

DevOps War Room is a 3-bot incident response team for Slack. An Incident Commander receives all alerts and requests, classifies severity, and routes to either a Log Analyzer (for error diagnosis via Sentry) or a Deploy Bot (for releases and rollbacks via GitHub + Railway).

When a Sentry alert fires at 3 AM, the team is already working on it.

What's included

3 pre-configured bots:

Incident Commander — Classifies severity (P0–P4), coordinates response, notifies on-call
Log Analyzer — Queries Sentry for stack traces, error frequency, affected users, and root cause
Deploy Bot — Handles deployments, rollbacks, CI status checks, and release management

2 keyword routing rules + 1 fallback:

Error alerts (error, exception, sentry, crash, 500, timeout) → Log Analyzer
Deploy requests (deploy, rollback, release, ci, pipeline, hotfix) → Deploy Bot
Everything else → Incident Commander

4 MCP integrations: Slack, Sentry, GitHub, Railway

How it works

The Incident Commander acts as the central coordination point. When it detects error-related keywords, it delegates to the Log Analyzer which pulls real data from Sentry — stack traces, error counts, affected user counts. For deployment requests, it routes to the Deploy Bot which checks CI status on GitHub before executing.

Every routing decision is logged in the delegation audit trail for post-mortem review.

When to use this template

You run services that need fast incident response
You use Sentry for error tracking and GitHub for CI/CD
You want automated severity classification and routing
You need a clear audit trail for post-mortems

psychology System Prompt

The instructions that define how this bot team behaves. It ships pre-configured — edit it anytime in your workspace.

You are the Incident Commander for a Slack-based DevOps war room.

## Core Behavior

You receive alerts, error reports, and deployment requests. Classify severity and route to the right specialist. Maintain calm, structured communication.

## Capabilities

### 1. Severity Classification
- Classify incidents as P0 (critical) through P4 (cosmetic)
- P0/P1: immediately notify on-call channel
- Include affected service and estimated impact in classification

### 2. Error Alert Routing
- Detect error reports, exceptions, stack traces, and monitoring alerts
- Route to Log Analyzer with relevant context
- Track investigation status and follow up on resolution

### 3. Deployment Coordination
- Detect deploy, rollback, and release requests
- Route to Deploy Bot with target version and environment
- Confirm deployment success and monitor for regression

### 4. Status Communication
- Post structured status updates to the incident channel
- Maintain an incident timeline for post-mortem
- Coordinate between Log Analyzer and Deploy Bot when both are involved

### 5. Escalation Management
- Escalate unresolved P0/P1 to human on-call via Slack mention
- Track time-to-resolution and flag SLA risks
- Coordinate rollback if deployment caused the incident

checklist Setup Guide

Quick Start

Set up your DevOps incident response team on Slack.

Step 1 — Create the Team

Go to Bot Teams → New Team. Name it "DevOps War Room".

Step 2 — Set Up the Incident Commander

Create the manager bot:

Platform: Slack
System prompt: Use the provided system prompt
MCP servers: Add mcp-slack and mcp-github

Step 3 — Set Up the Log Analyzer

Create the first specialist:

Platform: Slack
System prompt: "You are a Log Analyzer. When you receive error reports, query Sentry for stack traces, error frequency, affected users, and first/last seen timestamps. Provide a structured diagnosis: root cause hypothesis, affected services, and recommended fix."
MCP servers: Add mcp-slack and mcp-sentry
Add your Sentry auth token in secrets

Step 4 — Set Up the Deploy Bot

Create the second specialist:

Platform: Slack
System prompt: "You are a Deploy Bot. Handle deployment requests, rollbacks, and release management. Always check CI status on GitHub before any deploy. For rollbacks, confirm the target version and affected services before proceeding."
MCP servers: Add mcp-slack, mcp-github, and mcp-railway
Add your GitHub and Railway tokens

Step 5 — Configure Routing Rules

Error route (Priority 1): Keyword match — error, exception, sentry, alert, crash, 500, timeout, OOM → Log Analyzer
Deploy route (Priority 2): Keyword match — deploy, rollback, release, ci, pipeline, build, ship, hotfix → Deploy Bot
Fallback (Priority 99): Always → Incident Commander

Step 6 — Activate

Set all bots to Active. Consider connecting Sentry webhook alerts to trigger the team automatically.

Metadata

upgrade Version 1.0.0

description Type Bot Team

category Category Devops

code Platform slack

What's Included

check_circle 3 API keys needed

check_circle System Prompt

check_circle Setup Guide

Required MCPs

MCP servers this template connects to.

Author

Aerostack Official

verified

star 0

Frequently asked questions

What does the DevOps War Room template include? +

The DevOps War Room template is a pre-configured Aerostack workspace for devops. It bundles mcp-slack, mcp-sentry, mcp-github and any required workflows and edge functions. Install in one click and the workspace MCP URL is ready for Claude, Cursor, or any AI agent.

How do I install the DevOps War Room template? +

From the Aerostack marketplace page click Install — Aerostack creates a new workspace with every component pre-wired. You can also install via CLI: aerostack install template aerostack/devops-war-room

Can I customize DevOps War Room after installing? +

Yes. Every component (MCP servers, skills, workflows, agents) is individually editable from your workspace dashboard. Add, remove, or replace components — the template is a starting point, not a lock-in.

Is the DevOps War Room template free to use? +

Templates are free to install. Usage of included components is billed against your Aerostack plan — the free tier includes 500K AI tokens per month so most templates run for free at low volume.