Release Note Drafting with Codex: API Runtime Pattern
A production playbook for release note drafting in cross-industry operations using Codex: api runtime pattern, 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
Package the release note drafting instructions as a skill, send merged PRs, commits, issue links, and product context as run-scoped inputs, execute with Codex, 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 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.
Run request
POST /api/skills/<skill_id>/run
provider=codex
workflow=release-note-drafting
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo