release-manager — Claude-Code skill from Mr. Technology. ARCHITECT tier, audited and verified....

**TL;DR** - Orchestrate your release from code freeze to rollout. Don't miss a step.

The 10-Second Pitch

Coordinates the full release process: feature flags, rollouts, rollback triggers
Manages release trains with multiple services that need coordinated deploys
Tracks what's in each release, what changed, who needs to sign off
Integrates with deployment tooling to execute the actual rollout

Setup in 3 Steps

1. Define your release train: services, deploy order, approval gates

2. Configure feature flags and rollout criteria

3. Kick off the release and let it orchestrate with automatic rollback

**Example Prompt:**

Orchestrate the v3.2 release. Services: api-gateway, user-service, billing-service. Roll back if error rate exceeds 2%.

Pros	Cons
Turns release day from a stress-fest into a managed process	Requires well-defined deploy pipelines

Catches coordination mistakes	Complex rollbacks need practiced procedures

The difference between weekly and daily releases is process discipline. This provides the tooling layer.

Gives stakeholders a single view of release status	Still needs humans for novel failure modes