Skip to content
Development
Command

/deploy-release

Prepare and verify a staged or production deployment with rollback and smoke checks.

From plugin
agent-skills-standard
56521 skills21 agents21 commands1 MCP
Install
$ npx -y skills add hoangnguyen0403/agent-skills-standard --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/deploy-release

Context preview

What this command does when you run it.

Prepare and verify a staged or production deployment with rollback and smoke checks.

Command definition

deploy-release.md

Deploy Release

Prepare and verify a staged or production deployment with rollback and smoke checks.

**Input:** $ARGUMENTS

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

Instructions

Execute the following steps for **$ARGUMENTS**.

Deploy Release Workflow

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

Steps

1. Confirm readiness:

  • Verification report is PASS or accepted with documented risk.
  • Required approvals are present.
  • Migrations and feature flags are accounted for.
  • `release_confidence` is `high`, or `medium` with documented risk; `low` means NO-GO unless the release owner overrides in writing.

2. Prepare release:

  • Identify version, environment, deploy command, and owner.
  • Confirm secrets, config, queues, cron, and external services.
  • Define rollback command or revert path.

3. Deploy:

  • Run staging deploy first when available.
  • Run smoke checks before promotion.
  • Promote only when smoke checks pass.

4. Monitor:

  • Check logs, metrics, errors, latency, and core user flows.
  • Stop or roll back on defined failure signals.

5. Route:

  • 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.
  • Return BLOCKED only when required approvals, migrations, or rollback path are unresolved.

Handoff Payload

  • `slug`, `release_confidence`, release verdict (GO/NO-GO/ROLLED-BACK), smoke check results, 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
feature_status: implemented | blocked
requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence
completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: publish-notes | retro-learn

## Next Workflow

publish-notes | retro-learn

## Cost Report
Call `get_session_cost(workflow="deploy-release")` before final handoff.
Read more
Ships withagent-skills-standard

The portable SDLC standards layer for AI coding agents. Sync once, then work in your own runtime.

Get the whole plugin

Other commands on agent-skills-standard.