Runbook Execution with Claude Code: Result JSON Schema
A production playbook for runbook execution in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Operations teams automating repeatable SOPs
The problem
Operations teams automating repeatable SOPs need runbook execution to run repeatedly against runbooks, credentials policy, inputs, and escalation rules. 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 runbook execution 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 runbook execution, 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": "runbook execution completed",
"body": { "type": "runbook_execution", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo