Release Note Drafting with Claude Code: Result JSON Schema
A production playbook for release note drafting in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Developer relations and product teams
The problem
Developer relations and product teams need release note drafting to run repeatedly against merged PRs, commits, issue links, and product context. 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 note drafting 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 note drafting, 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 note drafting completed",
"body": { "type": "release_note_drafting", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo