Release It — Fleet Worker Edition

Use when assigned service resilience work applies.

When to Use

Assigned backend, service, integration or reliability work with a concrete failure mode. Skip for pure UI/docs/local logic without relevant runtime risk.

Prerequisites

Before applying any guidance, load references/fleet-worker-policy.md in full using read_file. The approved spec and repository conventions override book heuristics. This documentation skill installs nothing and is platform-neutral; language/tool examples require the target repository's own supported environment.

Procedure

1. Confirm assigned scope, acceptance criteria, current head and relevant repository instructions. Completion: the intended behavior and permitted files are explicit.
2. Map the assigned integration and its failure modes: slow responses, partial failures, resource exhaustion, repeated side effects. Inspect existing deadline, retry, idempotency, telemetry and rollout contracts first. Select only justified defenses within scope; obtain parameter values from approved policy and measurements rather than illustrative ranges. Distinguish required failure from authorized degradation, never mask auth/payment/config failures with fallback success. Verify cancellation, retry bounds and user-visible failure behavior in authorized environments. Deployment and chaos references support planning unless execution is separately authorized. Completion: the chosen change has a concrete task justification and defined checks.
3. Apply the smallest authorized change with patch; use terminal for real repository checks. Completion: each changed behavior and relevant error/auth path has evidence, or a named not-run/blocker reason; no fabricated results or numeric quality score.
4. Hand off the exact final head and evidence to SOL. Completion: worker report names outstanding gaps without claiming final acceptance. Terra is skipped. More than two failed SOL attempts on the same item triggers Opus actionable remediation, then renewed checks and SOL review at the new exact head.

References: Load Only the Applicable Detail

• anti patterns — use for anti patterns within the approved scope.
• capacity planning — use for capacity planning within the approved scope.
• chaos engineering — use for chaos engineering within the approved scope.
• deployment strategies — use for deployment strategies within the approved scope.
• observability — use for observability within the approved scope.
• stability patterns — use for stability patterns within the approved scope.

Pitfalls

No unsolicited features, refactors, redesign or infrastructure. Do not trade correct behavior for shorter functions, fewer arguments, empty-over-null substitutions, exceptions in a Result/Go-error codebase, or additional abstraction. Examples are illustrations, not verified results or settings for the target system.

Verification

Report assigned criteria, actual checks and their outcomes, relevant diffs, exact head and limitations. Tests and worker confidence do not replace SOL final review. See adaptation notes and upstream provenance for origin and changes.

---

Supporting files: this skill's supporting files are held in the docsite at docs/15-skills/_support/wondelai/release-it/ — fetch them fresh from jknash/docsite main alongside this page. Source: jknash/hermes-shared-skills · branch hermes-jkdev001 @ 1d0d545c3970 · skills/wondelai/release-it/ · view source · Imported 2026-10-03. Supporting files (references, scripts) remain in the source repository.

version 1.4.0-fleet.1 · author Wondel.ai (wondelai), Hermes Agent · license MIT.

Published by Muse · 2026-10-03.