/silver:release

Overview

/silver:release is the Silver Bullet orchestrator for milestone-level publishing. It handles versioned releases, changelogs, documentation updates, GitHub Releases, and milestone archival.

It never publishes directly — it orchestrates only. This workflow operates at the milestone level — it closes out a complete milestone, not a single phase.

silver:release uses the v0.48.3 APO catalog — it maps to WF-SILVER-RELEASE and finishes with AF-RELEASE. Design handoff and documentation are represented through catalog atomic flows and release workflow steps when UI milestone evidence requires them. This produces the design handoff package before the release is cut. See Composable Flows for the full catalog.

When to Use

Entry trigger signals for /silver:release:

"release" / "publish" / "version" / "go live"
"cut a release" / "tag v" / "ship to users" / "deploy to prod"
"changelog" / "release notes"

Ship disambiguation

Silver Bullet distinguishes between phase-level ship (silver:ship) and milestone-level release (silver:release) based on context signals:

Signal in your message	Route
Contains version number (v2.0, 1.4.0…)	`silver:release`
Contains "changelog" or "release notes"	`silver:release`
Contains "go live", "to production", "publicly"	`silver:release`
Active phase in progress, no version signal	`silver:ship` (phase merge)
No active phase, end of milestone	`silver:release`

Catalog execution (`WF-SILVER-RELEASE`)

Standard composition chain

WF-SILVER-RELEASE
  → AF-QUALITY-GATE → AF-REVIEW-REQUEST → AF-REVIEW → AF-REVIEW-TRIAGE
  → AF-VERIFY → AF-SECURE → AF-VALIDATE
  → AF-BRANCH-FINISH → AF-COMPLETION-AUDIT → AF-SHIP
  → AF-RELEASE → silver:create-release (last)

`AF-RELEASE` sub-steps

Pre-release quality gate — AF-QUALITY-GATE plus domain audit evidence.
UAT and milestone audits — AF-VERIFY checks cross-phase evidence and release readiness artifacts.
Gap closure — dynamic insertion of AF-PLAN, AF-EXECUTE, and AF-DEBUG repair atoms when the release V-gate finds missing work.
Documentation and handoff — AF-DOCUMENT updates durable docs and release handoff evidence.
Ship prep — AF-BRANCH-FINISH → AF-COMPLETION-AUDIT → AF-SHIP.
Create release — silver:create-release runs after release V-loop evidence and milestone archival are complete.

Gap-closure loop (max 2 iterations)

When milestone audit finds gaps: silver:plan for gap phases → nested silver:feature per gap → return to AF-QUALITY-GATE pre-release quality gate. After 2 iterations with remaining gaps, SB presents: release anyway / extend milestone / abort.

Delivery tail (orchestrator parent mode)

When orchestrator_mode is parent, the catalog delivery tail runs automatically (AF-QUALITY-GATE → review → verify → secure → ship prep → silver:create-release). Audit, UAT, milestone, and gap-closure steps remain parent-driven.

Non-Skippable Gates

🔒

These steps cannot be skipped regardless of §10 preferences or user request:

/silver:quality-gates pre-release (AF-QUALITY-GATE)
/verify-tests fresh release-session test run (AF-VERIFY)
security (AF-SECURE) is mandatory for every release
silver:ship (AF-SHIP) must succeed before milestone archival
/silver:create-release runs only after AF-RELEASE evidence and milestone archival

Example Invocation

/silver:release Cut v0.39.0

Silver Bullet routes to release workflow. Pre-release quality gates → UAT audit → milestone audit → security hard gate → docs and milestone summary → cross-artifact review → deploy readiness → fresh tests → silver:ship → milestone archival → /silver:create-release → post-release items summary.

← Previous /silver:deep-research Next → /silver:fast