Production Readiness Review with Claude Code: API Runtime Pattern
A production playbook for production readiness review in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Engineering leaders approving agent launch
The problem
Engineering leaders approving agent launch need production readiness review to run repeatedly against architecture docs, threat models, test results, and runbooks. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the production readiness review instructions as a skill, send architecture docs, threat models, test results, and runbooks as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For production readiness review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=production-readiness-review
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo