Agent Skills: Deploy Release Skill

Deploy Release Skill

[!IMPORTANT] Prepare and verify a staged or production deployment with rollback and smoke checks.

Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

When the user asks to perform this workflow, execute the following steps:

Deploy Release Workflow

Goal: Ship verified work with explicit deployment steps, smoke checks, and rollback criteria.

Steps

1. Confirm readiness (STLC Stage 6 Closure):
   • Verify test cycle closure summary, open defect ledger, and residual-risk ledger per skills/quality-engineering/quality-engineering-test-plan-authoring/references/lifecycle-and-roles.md. Technical PASS confirms verification only; named release owner authorization is required.
   • Mobile release gates (Contract C6): verify build artifact digest/version, release signing/distribution context, and device smoke checks. Missing build artifacts or drivers cannot be replaced by web evidence.
   • Migrations, feature flags, and product evidence contracts accounted for (evidence.json measurement owner, MET baseline, instrumentation, guardrails).
   • release_confidence is high, or medium with documented risk; low is NO-GO without written release owner override.
   • Identify version, environment, deploy command, and owner.
   • Confirm secrets, config, queues, cron, and external services.
   • Define rollback command or revert path.
   • Environment tier: dev deploys freely; staging deploys behind the smoke gate; production is prepared by the agent and authorized by the named release owner through the guardrail approval gate.
2. Deploy:
   • Run staging deploy first when available.
   • Rehearse the rollback in staging before promoting to production.
   • Run smoke checks before promotion.
   • Promote only when smoke checks pass.
3. Monitor:
   • Check logs, metrics, errors, latency, and core user flows.
   • Guardrail harm or regression escalates immediately to authorized incident controls (incident-hotfix); stop or roll back on defined failure signals.
4. Persist and route:
   • Write run record to artifacts/runs/[slug]/[compactISO]-deploy-release.json when file writes allowed. Feature feature_status=released is preserved even when product value observations remain pending or inconclusive.
   • User-facing notes -> publish-notes.
   • Process and standards feedback -> retro-learn.

Runtime Contract

• Use once verification/UAT signoff is PASS and a release window is open.
• Required inputs: verification report plus release version, environment, and rollback path. Proposal in ledger is not host deployment authorization.
• Return BLOCKED when required approvals, migrations, or rollback path are unresolved, when a production deploy has no named authorizer, or when a product-evidence initiative lacks a registered MET baseline (or scoped exception), measurement owner, instrumentation, guardrails, or review trigger. Feature released status is retained when product value is pending or inconclusive.

Handoff Payload

• slug, release_confidence, release verdict (GO/NO-GO/ROLLED-BACK), smoke check results, measurement contract refs when present, rollback path, outcome report, next workflow.

Blocking Questions

• Ask max 3 at a time with a recommended default and 2-3 options.

Output Template

# Deployment Report: [Name]

## Release Verdict
GO | NO-GO | ROLLED-BACK

## Release

## Environments

## Commands

## Smoke Checks

| Check | Result | Evidence |
| --- | --- | --- |
| [check] | [PASS/FAIL/BLOCKED] | [evidence] |

## Rollback

## Outcome Report
{schema_version: 1, run_id: "[run-id]", slug: "[slug]", workflow: deploy-release, feature_status: released, started_at: "[timestamp]", completed_at: "[timestamp]", requirement_trace: {brd_objectives: [], requirements: [], acceptance_criteria: [], srs: []}, completed_evidence: [], missing_evidence: [], decision_needed: [], recommended_next_workflow: publish-notes, cost: {source: unavailable}, agent: {identity: "[agent-identity]", model: "[model]"}}

## Next Workflow

publish-notes | retro-learn

## Cost Report
Call `get_session_cost(workflow="deploy-release")` before final handoff.