Design Spec Review with Claude Code: Result JSON Schema
A production playbook for design spec review in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Product engineering teams
The problem
Product engineering teams need design spec review to run repeatedly against specs, screenshots, Figma exports, and acceptance 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 design spec 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 design spec 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": "design spec review completed",
"body": { "type": "design_spec_review", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo