Workflow Retry Design with Claude Code: Result JSON Schema

A production playbook for workflow retry design in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: Backend engineers building reliable agents

The problem

Backend engineers building reliable agents need workflow retry design to run repeatedly against terminal states, retry policies, idempotency keys, and failure logs. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Define the outer result contract once, let the workflow retry design skill own body.data, and reject terminal output that does not match the expected schema.

Tradeoffs and failure modes

Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For workflow retry design, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Result shape

{
  "schema_version": "argo.result.v1",
  "summary": "workflow retry design completed",
  "body": { "type": "workflow_retry_design", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo