Release Blocker Review with Claude Code: Result JSON Schema
A production playbook for release blocker review in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Engineering managers preparing release decisions
The problem
Engineering managers preparing release decisions need release blocker review to run repeatedly against tickets, CI results, incidents, and launch criteria. 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 release blocker review 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 release blocker review, 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": "release blocker review completed",
"body": { "type": "release_blocker_review", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo