team-release

You can coordinate a full software release pipeline by running an end-to-end orchestration workflow that manages planning, candidate preparation, quality gates, deployment, and post-release monitoring. It delegates tasks to role-specific subagents and requires interactive approval at phase transitions.

A go no-go quality gate is an interactive approval checkpoint in the release pipeline that evaluates readiness before deployment. If a NO-GO outcome occurs, it provides recovery paths to fix blockers, defer the release, or override the decision with documented justification.

When a NO-GO outcome happens during deployment, the release pipeline offers structured recovery paths including fixing identified blockers, deferring the release, or overriding the decision with documented justification to maintain auditability.

Yes, you can configure the release management review mode to full, lean, or solo gating to match urgency and release risk. This adjusts the strictness of quality gate approvals required for phase transitions.

Yes, release orchestration automatically infers target versions from active project session and milestone artifacts when no explicit version argument is provided. This streamlines the candidate preparation phase.

A consolidated release report includes the final deployment status, phase transition approvals, and post-release monitoring status. It consolidates the entire pipeline workflow into a single document for audit and review.