deployment-readiness

Deployment readiness checks standardize release validation by embedding GitHub-aware checklists into PR descriptions. This Skill applies readiness gates to release trains, hotfix reviews, and deployment PRs, validating scope, quality signals, communications, and operational readiness while outputting release gate markdown snippets and rollout scorecards.

A deployment gate checklist validates scope coverage, quality signals, stakeholder communications, documentation completeness, and operational readiness. This Skill generates GitHub-ready gate templates that track blockers via minister-tracker integration and produce QA handshake summaries alongside release gate snippets for visibility before deployment.

Yes. Deployment gates apply to release trains, hotfix reviews, stakeholder briefings, and deployment PRs. This Skill embeds standardized readiness validation into each context, auto-filling blockers and outputting consistent release gate markdown, QA summaries, and rollout scorecards across all release scenarios.

Deployment blockers are tracked via minister-tracker integration, which auto-fills blocker status within PR checklists. This Skill applies blocker tracking alongside scope, quality, and operational readiness validation, surfacing blockers in release gate markdown and rollout scorecards for early visibility.

Deployment readiness gates produce three outputs: a release gate markdown snippet for PR embedding, a QA handshake summary documenting quality signals and sign-offs, and a rollout scorecard capturing scope, communications, and operational readiness status.

Mirror deployment gates into PR descriptions early in the release cycle for visibility across release trains, hotfix reviews, and stakeholder briefings. Early gate visibility enables blockers to surface before deployment, allowing teams to validate scope, quality, communications, and operational readiness in parallel with development.