Skip to Content
Cheat Sheet/release-decision

/release-decision

The explicit go/no-go gate before a release — the structured recommendation that says ship now, wait with named conditions, or don’t ship.

When to use it

Run this when a release is candidate-ready and the question is “should we actually ship it?” The agile-product-manager agent reads the milestone definition (from docs/PRODUCT-ROADMAP.md), the test validation results (from /test-feature or the CI suite), the production baseline (from Sentry if configured, or the curl-probe fallback), and the milestone health report (from /check-milestone). It produces a structured recommendation: SHIP / HOLD / NO-SHIP with rationale naming the gates that passed and the ones that failed.

The output is not a unilateral decision — it’s a recommendation designed to give the operator the information needed to make the real call. The agent doesn’t ship; the operator does.

Use this for whole-release decisions (the next minor version, the M1 launch, the production cutover). For per-PR ship decisions, the agent-merge gate (or human merge click) is the gate. For per-feature visibility flips (safety:flagged morning toggles), the operator makes the call directly.

Don’t run this without the upstream artifacts (milestone health, test validation, production baseline). With nothing to read, the recommendation degenerates to opinion. The Plan / Implement / Review phases populate the substrate this command consumes.

How it fits

Inputs converge from the milestone gate, the test gate, and the production baseline. Output is a structured SHIP / HOLD / NO-SHIP recommendation that the operator acts on.

What it does (quick)

  • Reads the milestone definition + health report
  • Reads the latest test validation results
  • Reads the production baseline (Sentry if configured; curl probe as fallback per docs/testing/sentry-gating.md + render-gating.md)
  • Evaluates each gate against its criteria (milestone exit met? validation green? production healthy?)
  • Produces a structured recommendation: SHIP / HOLD / NO-SHIP, naming the passing and failing gates explicitly
  • Outputs in a form the operator can copy verbatim into a release announcement or into the team’s decision log
  • /check-milestone — upstream gate #1 (milestone exit criteria)
  • /test-feature — upstream gate #2 (feature-level validation)
  • /log-session — the natural successor; capture the release decision in the journal

Canonical spec: .claude/commands/release-decision.md

Last updated on
/test-feature/log-session