team-release

Coordinate multi-role software releases from planning through deployment with YAML-defined orchestration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of running a reliable, multi-role software release by coordinating planning, quality gates, decision-making, and deployment across the right stakeholders.

Core Features & Use Cases

  • Release orchestration pipeline: Drives a structured sequence from planning through go/no-go to deployment, with explicit phase transitions.
  • Parallel quality gates: Runs QA, build/artifacts, and optional security/network sign-offs concurrently to reduce release cycle time.
  • Version discovery and approval: If no version is provided, attempts to infer from production session state and milestones and confirms the result with the user.
  • User-controlled decision points: Uses user prompts to present agent proposals and requires approval before advancing phases.

Quick Start

Invoke the team-release skill with version "next" to run the release pipeline and pause for approvals at each major decision point.

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 multi-role software release pipeline with parallel quality gates?

Multi-role software release coordination uses YAML-defined orchestration logic to drive planning, parallel QA and build artifact sign-offs, and controlled deployment. Interactive decision checkpoints pause the pipeline for user approval before advancing through phase transitions.

How do I handle release versioning when the version number is missing?

Release versioning handles missing numbers by attempting inference from production session state and milestones. The inferred version is then presented to the user via interactive prompts for explicit confirmation before proceeding with the deployment pipeline.

What is the best way to orchestrate go/no-go decisions during a software deployment?

Go/no-go decisions during software deployment use interactive user prompts to present agent proposals and require explicit approval. This controlled decisioning connects parallel quality gate execution to post-release monitoring within the release orchestration pipeline.

Can I run QA sign-off and security audits concurrently to reduce release cycle time?

QA sign-off and security audits run concurrently as parallel quality gates to reduce release cycle time. The orchestration pipeline drives build artifact checks and optional security network sign-offs simultaneously before presenting results for go/no-go decisioning.

When do I need YAML-defined orchestration logic for project orchestration?

YAML-defined orchestration logic is needed for project orchestration when coordinating a structured sequence from release candidate preparation through deployment. It manages parallel quality gate execution, version inference, and interactive decision checkpoints for controlled phase transitions.