Deploy Release Skill
[!IMPORTANT] Dispatch provider-neutral cloud operations and verify staged or production releases with rollback and smoke checks.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, 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: Execute one authorized cloud operation, or ship verified work with explicit deployment steps, smoke checks, and rollback criteria.
Steps
- Parse, load, and gate:
- Accept
operation=setup | deploy | verify | monitor | diagnose | recover. Default todeployonly when genuinely omitted; reject unknown, conflicting, or typo modes before any provider call. - Resolve
common-devops-operationsthrough the AGS MCPget_skill(category="common", name="common-devops-operations")when available, else from the consumer's supported installed-skill location; resolve its references and the operations-report reference relative to that loaded skill. If the contract cannot be obtained, block affected execution instead of improvising authorization. - Classify by actual effect, never the label: any promotion, traffic switch, or configuration change introducing a new release is deploy-bearing and enters step 3 even under
setuporrecover;recovercannot introduce an unverified build.verify,monitor, anddiagnosestay read-only, and a mutation request blocks for reclassification plus renewed authorization. - Fresh task-linked active harm gate: before any ordinary dispatch or execution, hand ownership to
incident-hotfix, which chooses and authorizes mitigation. An existing incident-owned fixed grant executes once through the shared procedure and returns here; no recursive intake.
- Accept
- Execute non-release effects:
verify,monitor,diagnose,setup, and a fixedrecoverrun only their own classified, authorized action set through the shared procedure, with outward verification where that operation defines it. This branch never stages, rehearses, or promotes a release.
- Release readiness (deploy-bearing effects only):
- Test-cycle closure summary, open-defect ledger, and residual-risk ledger verified against the loaded
quality-engineering-test-plan-authoringreferences/lifecycle-and-roles.md; carrydelivery_mode, work-item plus released revision, technical verification ref, and business acceptance ref ornot assessed. Technical PASS or acceptance never grants deployment authority. - Production promotion requires a named release owner's scoped authorization; for cloud operations, staging and dev mutations need their own bound grant too. No environment deploys freely, and a merge event is not an approval.
- Mobile release gates (Contract C6): build artifact digest/version, release signing/distribution context, and device smoke checks. Missing build artifacts or drivers cannot be replaced with web evidence. Mixed mobile/backend action sets classify each action independently; cloud MCP gaps never erase C6 or block unrelated distribution.
- Migrations and feature flags are accounted for alongside measurement contracts; with product evidence (
docs/product/<slug>/evidence.json), carry measurement owner, registered MET baseline or exact scoped exception DEC, query, instrumentation, cohort, window, guardrails, and review trigger; never fabricate baselines, approval, or causal ROI. release_confidenceishigh, ormediumwith documented risk;lowis NO-GO without a written release-owner override.
- Test-cycle closure summary, open-defect ledger, and residual-risk ledger verified against the loaded
- Prepare, stage, promote, and inspect:
- Identify version, environment, action set, artifact identity, owner, and rollback command or revert path; confirm secrets, config, queues, cron, and external services.
- Deploy to staging first when available, rehearse the rollback there, and run smoke checks; promote only when smoke passes.
- Set a bounded post-release observation window; after promotion, inspect applicable provider logs, metrics, errors, latency, and core user flows. Record telemetry gaps explicitly; missing telemetry is not healthy. Failure signals stop rollout and route to
incident-hotfix; roll back per defined criteria. - Recheck target, principal continuity, permission, approval expiry, and fresh harm immediately before promotion; reconcile actual resource state after any timeout before retrying; verify the live target origin, never a provider success flag alone.
- Stop on harm and route ownership:
- Active harm stops promotion and hands to
incident-hotfix; statistical control bands and scan deltas belong tomonitor-respond, and a discrete failed build or expired certificate needs no statistical baseline.
- Active harm stops promotion and hands to
- Persist and route:
- Emit one operations report in the shared evidence shape, and add the run record below only for a verified, authorized release.
- Non-deploy operations preserve the prior evidenced lifecycle and never advance or downgrade it; an operations receipt is never a release or rollback record. Without lifecycle evidence, emit operations evidence only (
feature_lifecycle: not_assessed, no feature run record). - Hand to
publish-notesonly with release evidence; otherwiserecommended_next_workflow: nullandnext_action: none.
Runtime Contract
- Use for cloud or hosting operations and any release promotion; an unspecified mode means
deploy. Required inputs: operation mode, target/principal scope, and, for deploy-bearing effects, verification, acceptance reference, release authority, and rollback path. - Return BLOCKED with the exact reason (
missing_mcp,disconnected_mcp,unauthenticated,wrong_target,missing_capability,permission_denied,approval_required,approval_expired,unsupported_enforcement,uncertain_write,verification_failed). Offline document review may continue under an explicit evidence limit; it never counts as operational proof.
Handoff Payload
slug,operation, classified effect, target/principal scope,delivery_mode, work-item reference plus revision, technical and acceptance refs (not assessedwhen absent), release authority reference,release_confidence, verdict (GO/NO-GO/ROLLED-BACK), smoke results, measurement refs, artifact identity, rollback path, operations report, outcome report,next_action.
Blocking Questions
- Ask max 3 at a time with a recommended default and 2-3 options.
Output Template
# Operations And Deployment Report: [Name]
## Decision Brief
- Operation + classified effect: [setup | deploy | verify | monitor | diagnose | recover] / [read_only | config_mutation | deploy_bearing]
- Work item: [ref @ revision]; delivery mode: brief | standard | extended; versions, environments, and commands: [refs]
- Technical verification: [ref]; business acceptance: [ref or not assessed]; release authority: [owner/ref @ expiry]
## Operations Report
- Target / principal: [scope]; artifact or resource: [digest/ARN]; capabilities: [tools]; outcome: [completed | failed | blocked | uncertain_write + reason]
- Feature lifecycle: [preserved: <state> | not_assessed | advanced: released]; next action: [none | step]
## Release Verdict
GO | NO-GO | ROLLED-BACK
## 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 | incident-hotfix
## Cost Report
Call `get_session_cost(workflow="deploy-release")` before final handoff.