team-release

Orchestrate a software release pipeline with quality gates and go/no-go decisions.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill team-release-imclab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-release
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/team-release
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill team-release-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the chaos and risk of shipping releases without structured planning, QA sign-off, and deployment coordination by orchestrating a dedicated release pipeline.

Core Features & Use Cases

  • Release orchestration: Coordinates producers, release-manager, and go/no-go decision flow to execute a release from candidate to deployment.
  • Quality gates in parallel: Runs QA regression, build/artifact verification, and optional security/network checks to prevent common release failures.
  • Operational readiness: Produces release checklists, changelog and patch notes, and verifies analytics telemetry readiness for the release build.

Quick Start

Use the team-release skill with the version argument next to orchestrate a full release pipeline including quality gate checks and a final go/no-go decision.

Frequently Asked Questions about team-release

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

FAQPage Schema
How do I orchestrate a software release from candidate build to deployment?▼

Release orchestration coordinates the entire pipeline by guiding candidate preparation, running quality gates, and executing a go/no-go decision flow before final deployment.

What quality gates should I run before a production deployment?▼

Before production deployment, you should run QA regression, build and artifact verification, and optional security or network checks to prevent common release failures.

How do I automate go/no-go decisions for versioned builds?▼

Automate go/no-go decisions by requiring explicit user confirmation for phase transitions, ensuring all quality gates and telemetry readiness checks pass before proceeding.

How do I verify analytics telemetry readiness for a release build?▼

Telemetry readiness verification checks if analytics instrumentation is properly configured in the release build, ensuring operational tracking is active before deployment.

Can I infer the target version for release management from session state?▼

Yes, when a target version is omitted, the release manager can infer it from production environment data and session-state milestones to automatically proceed with orchestration.

What is the best way to generate patch notes and release checklists for game teams?▼

Generate patch notes and release checklists as part of operational readiness, producing standardized changelog documentation alongside build verification for repeatable releases.