testland/release-runbook-author
Turns one service's release into a written six-phase runbook: pre-flight checks, a smoke gate, a canary observation window, a named human promote gate, progressive rollout, and post-release verification. Fixes each phase's pass criteria as a delta against a recorded baseline rather than a bare absolute number, gives canary and rollout separate windows and separate thresholds, and emits a per-phase evidence table that becomes the release record. Use when a single service is about to ship and its release steps exist only as tribal knowledge or a chat thread, so nobody can say in advance what evidence promotes it, what evidence halts it, or who decides.
75
94%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
output-template.mdreferences/
Output template
One document. It is the plan before the release and the record after it.
# Release runbook - {service} {version}
**Promote-gate owner:** {one named person, availability window}
**Last known good artifact:** {id}
**Recovery rule:** a crossed threshold halts the phase and puts a recovery
decision to {owner}. Recovery may be roll back, roll forward, or redeploy
last known good, and only {owner} chooses which.
## Baseline - recorded {window} before deploy
| Metric | Value | Query |
|--------|-------|-------|
## Thresholds
| Metric | Absolute floor | Ratio limit (canary vs control) | Ratio limit (rollout vs baseline) |
|--------|----------------|----------------------------------|------------------------------------|
## Phase 1 - Pre-flight
| Check | Verdict | Evidence |
|-------|---------|----------|
## Phase 2 - Smoke gate
**Command:** **Environment:** **Duration:** **Result:**
## Phase 3 - Canary ({share} traffic, {window}, coverage: smoke | bake)
| Metric | Absolute floor | Ratio limit | Control | Canary | Ratio | Verdict |
|--------|----------------|-------------|---------|--------|-------|---------|
**Anomalies below threshold:**
**Verdict:** PASS | PROCEED WITH CAUTION | HALT
## Phase 4 - Promote gate
**Decision:** continue | pause | rollback
**Made by:** **At:** **On this evidence:**
**Acknowledged anomalies carried forward:**
## Phase 5 - Rollout
| Stage | Share | Window | Metrics vs baseline | Verdict |
|-------|-------|--------|---------------------|---------|
## Phase 6 - Post-release
| Metric | Baseline | Observed | Ratio | Verdict |
|--------|----------|----------|-------|---------|
**Administrative tail:** tag / changelog / notification, each with a timestamp.
## Follow-ups
- [ ] {product defects acknowledged at the promote gate}
- [ ] {runbook defects the release exposed}