team-release

Orchestrate multi-role release pipelines from candidate to deployment with decision gates.

3|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill team-release-negentropy-laby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-release
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/team-release
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill team-release-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the release team to execute a release from candidate to deployment, coordinating roles and governance to ensure a controlled, auditable rollout.

Core Features & Use Cases

  • Multi-role coordination: release-manager, qa-lead, devops-engineer, security-engineer, analytics-engineer, community-manager, and producer collaborate across the release pipeline.
  • Phase-driven workflow: structured stages from planning, candidate creation, quality gates, localization/analytics, to go/no-go decision.
  • Decision governance: uses AskUserQuestion prompts to surface subagent proposals and requires explicit user approvals before phase transitions.
  • Outputs and traceability: creates release artifacts, memory-bank updates, and an auditable deployment record.
  • Memory and governance: a memory_bank is consulted for release governance and post-release evidence tracking.

Quick Start

Invoke the team-release skill with a version number or 'next' to begin coordinating the release pipeline.

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 production deploy across multiple roles like release management and QA?▼

Coordinating a production deploy across multiple roles requires orchestrating a release team through a structured pipeline. This skill assigns subagents to roles like release-manager, qa-lead, and devops-engineer, executing stages from candidate creation to deployment with explicit decision gates.

What is a go-no-go decision gate in release orchestration?▼

A go-no-go decision gate in release orchestration is a checkpoint requiring explicit user approval before phase transitions. This skill surfaces subagent proposals via prompts, ensuring controlled governance and auditable traceability before proceeding to production deployment.

How do I ensure release traceability and track post-release evidence?▼

Release traceability is ensured by consulting a memory-bank for governance and tracking post-release evidence. This skill generates auditable deployment records and updates the memory-bank continuously across all release pipeline phases.

Can I use release orchestration for coordinated product releases involving design review and analytics?▼

Release orchestration supports coordinated product releases involving design review, testing, localization, and analytics. This skill structures these stages into a multi-phase pipeline, applying governance gates to ensure a controlled rollout across all involved teams.

What is the best way to automate stakeholder communication during a software rollout?▼

Automating stakeholder communication during a software rollout is best handled through a phase-driven workflow with role-specific subagents. This skill integrates a community-manager and producer to coordinate updates, capturing governance decisions and outputs for full traceability.

How do I start a release pipeline using version tracking?▼

To start a release pipeline using version tracking, invoke the skill with a specific version number or 'next'. This initiates the orchestration workflow, triggering the multi-role team to begin processing the release candidate through quality gates to deployment.