team-release

Coordinate software release workflows from candidate selection through production deployment.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill team-release-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-release
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/team-release
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill team-release-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the coordination burden of managing a software release across planning, quality checks, deployment, and post-release follow-up.

Core Features & Use Cases

  • Release Orchestration: Coordinates release-manager, QA, DevOps, security, analytics, and producer decisions through a structured phase pipeline.
  • Risk-Gated Execution: Handles version discovery, approvals, go/no-go decisions, blocker escalation, and rollback-aware deployment paths.
  • Operational Communication: Produces release notes, stakeholder updates, and post-release monitoring guidance for a controlled launch.
  • Use Case: A team preparing a product update can use this Skill to move from release candidate to production while capturing sign-offs and evidence.

Quick Start

Use the team-release skill to coordinate release v1.2.3 from candidate planning through QA, deployment, and post-release monitoring.

Frequently Asked Questions about team-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate a software release from candidate selection to production deployment?

Software release coordination moves a versioned product launch through planning, quality gates, build verification, stakeholder approval, and deployment. This workflow requires structured handoffs, user confirmations, and rollback-aware decisions to safely reach production.

What is a risk-gated release workflow and when do I need it for versioned product launches?

A risk-gated release workflow applies go/no-go decisions, blocker escalation, and rollback-aware deployment paths to versioned product launches. You need it when coordinating across release-manager, QA, DevOps, security, analytics, and producer decisions requires structured phase pipelines.

How do I manage stakeholder approvals and sign-offs during a deployment pipeline?

Managing stakeholder approvals during a deployment pipeline requires structured handoffs and explicit user confirmations across release-manager, QA, DevOps, and producer roles. Risk-gated execution captures sign-offs and optional release evidence for a controlled launch.

Can I automate release notes and stakeholder updates for post-release monitoring?

Release notes and stakeholder updates are produced as operational communication during a controlled launch. Post-release monitoring guidance is generated to track the deployment outcome, ensuring the release workflow captures evidence and communicates status.

Does team-release support rollback-aware deployment paths for DevOps teams?

Rollback-aware deployment paths are supported for DevOps teams coordinating versioned product launches. The workflow handles version discovery, approvals, go/no-go decisions, and blocker escalation to ensure production deployments include safe rollback options.

What's the best way to track release evidence and quality gates across QA and DevOps?

Tracking release evidence across QA and DevOps requires a structured phase pipeline that handles build verification, stakeholder approval, and quality gates. Optional release evidence tracking captures sign-offs and decisions throughout the deployment workflow.