Orchestrate a multi-role software release workflow from planning through deployment.
npx skills add https://github.com/WindXRan/y3td --skill team-release-windxran
Please help me install this Agent Skill. Skill: team-release Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/team-release Command: npx skills add https://github.com/WindXRan/y3td --skill team-release-windxran
This Skill removes the chaos of coordinating a multi-role release by orchestrating planning, candidate preparation, quality gates, and deployment decisions through a structured pipeline with explicit user approvals.
Run team-release with a version number (for example, v1.2.3) and follow the approval prompts to proceed through planning, candidate, quality gates, go/no-go, and deployment.
High-intent search queries and answers about installing and using this skill.
You can coordinate a multi-role software release workflow by running a structured pipeline that manages release candidate preparation, parallel quality gates, and explicit go/no-go approvals. This orchestrates planning through deployment and post-release monitoring.
A go/no-go decision for versioned releases consolidates results from parallel QA regression, build readiness, and security gates. It requires explicit user approval to transition phases, ensuring all quality checks pass before tagging and deploying to staging or production.
You can run parallel QA regression and security audits by executing configurable quality gates during the release candidate phase. The workflow consolidates build readiness, network stability, and security check results for a final deployment decision.
Yes, you can automate release branch freezing and version bumping during candidate preparation. The workflow cuts a release branch, infers or confirms the version number, generates a checklist, and freezes the branch to prevent scope creep before quality gates run.
Yes, the release orchestration pipeline supports delegated artifact, changelog, and patch-notes generation. If the go/no-go decision is approved, it tags and deploys while preparing community messaging and announcements in parallel.
The structured approval pipeline requires version inference or user confirmation and explicit phase transitions, meaning it cannot bypass quality gates or auto-deploy without manual go/no-go approval. Configurable review modes must be set to match your team's workflows.
tsunami28Measure line coverage and validate acceptance criteria tests before release.
OpenLaborAutomate production deployments with rollback-ready workflows and guardrails.
pcsensorOrchestrate parallel subagents with isolated contexts and two-stage reviews.
MichaelSolatiAutomate end-to-end game release workflows with structured phase gates and go/no-go decisions.
