Marketing: Content Refresh Brief Generation with Claude Code: API Runtime Pattern
A production playbook for content refresh brief generation in marketing operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Content marketing teams
The problem
Content marketing teams need content refresh brief generation to run repeatedly against old articles, analytics exports, product notes, and competitor examples. In marketing operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the content refresh brief generation instructions as a skill, send old articles, analytics exports, product notes, and competitor examples 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 content refresh brief generation, 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=marketing-content-refresh
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo