Release Note Drafting with Codex: SKILL.md Template
A production playbook for release note drafting in cross-industry operations using Codex: skill.md template, 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
Put the operating procedure in SKILL.md, keep examples beside the skill, attach merged PRs, commits, issue links, and product context per run, and let Argo turn the folder into a repeatable Codex execution.
Tradeoffs and failure modes
A skill folder is less flexible than an open chat, but it gives the product a versioned workflow that can be tested and rolled back. 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.
SKILL.md starter
# SKILL.md
You run release note drafting using Codex.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "release_note_drafting".
Run this on Argo