Status Dispatcher

Dispatch a comprehensive status check across your project infrastructure, services, deployments, and task orchestration state in a single command.

When to Use This Command

Run this command when...

• You need to check the current state of deployments, services, or infrastructure before making changes
• You are starting a work session and want a quick overview of project health across all environments
• A deployment just completed and you want to verify services are running correctly
• You need to check Railway, Vercel, or other platform statuses before pushing updates
• You want a consolidated view of task progress, branch state, and environment health

Quick Start

Copy
# .claude/commands/status-dispatcher.md
---
name: Status Dispatcher
description: Check project status across services, deployments, and tasks
command: true
---
Check status: $ARGUMENTS

Gather status from all configured sources:
- Deployment platforms (Railway, Vercel, AWS)
- Git branch and commit state
- Task orchestration progress
- Environment health checks

Copy
# Invoke the command
claude "/status-dispatcher"

# Expected output
# > Checking project status...
# > Git: branch feature/auth (3 commits ahead of main)
# > Railway: production (healthy), staging (deploying)
# > Tasks: 8/14 completed, 2 in-progress, 4 pending
# > Environments:
# >   production: API healthy (142ms), DB connected
# >   staging: deploying commit abc1234 (ETA: 2min)
# > No critical issues detected.

Core Concepts

Concept	Description
Multi-Source Polling	Queries git, deployment platforms, and task state in a single pass
Health Assessment	Evaluates service health through endpoint checks and status APIs
Environment Comparison	Shows side-by-side status of production, staging, and development environments
Deployment Tracking	Reports current deployment state, recent deploys, and pending changes
Alert Surfacing	Highlights critical issues, failing services, or blocked tasks prominently

Status Dispatcher Flow
=======================

  [Git State]   [Deploy Platform]   [Task State]   [Health Checks]
       |               |                 |                |
       v               v                 v                v
  +---------------------------------------------------------+
  |              Status Aggregation Engine                  |
  +---------------------------------------------------------+
                         |
                    [Consolidate]
                         |
              +----------+----------+
              |          |          |
          Healthy    Warning    Critical
          (green)    (yellow)   (red)
              |          |          |
              +-----+----+----+----+
                    |         |
               Summary    Alert List

Configuration

Parameter	Description	Default	Example	Required
$ARGUMENTS	Specific service or area to check	all services	"railway production"	No
platform	Deployment platform to query	auto-detect	"railway", "vercel"	No
include_tasks	Include orchestration task status	true	false	No
health_check_timeout	Timeout for endpoint health checks in seconds	10	30	No
verbose	Show detailed status for each service	false	true	No

Best Practices

1. Run before every deployment -- Check status before pushing changes to catch existing issues that might be confused with new deployment problems.

2. Use specific arguments for focused checks -- "/status-dispatcher railway staging" is faster than a full status sweep when you only need one platform.

3. Automate daily status checks -- Schedule the status dispatcher as part of your morning routine to catch overnight failures or stale deployments early.

4. Monitor after infrastructure changes -- After updating environment variables, scaling services, or modifying configurations, run a status check to verify everything applied correctly.

5. Combine with report commands -- Feed status data into the report runner for formatted status reports suitable for team standups or stakeholder updates.

Common Issues

Platform CLI not authenticated: Status checks for Railway, Vercel, or AWS require authenticated CLI tools. Run railway login, vercel login, or aws configure before using this command.

Health check timeouts on cold starts: Serverless or auto-scaling services may not respond within the default timeout after periods of inactivity. Increase health_check_timeout for such environments.

Stale task state: If orchestration directories are from a previous session and tasks were completed outside of Claude, the task status may not reflect reality. Run a sync command first to reconcile.