What problem does it solve? Content publishing pipelines often exist only as tribal knowledge, so sessions skip steps, treat a curated lane like an autonomous queue, or send the owner a rendered artifact instead of a real preview link. This Skill writes down the full lane a piece travels — from owner interview at capture to live release — naming which steps run unattended and which wait on the owner. ## Core Features & Use Cases - End-to-end pipeline definition: Ten named steps (capture, description closure, selection, draft, bounded review rounds, merge gate, held preview, release, social pair) each labeled AFK, HITL, or otherwise, so nobody discovers owner-waiting steps by accident. - Held preview mechanics: Documents the draft: true front-matter flag, the ?preview URL parameter, per-edition slug rules for composing the review link, and why HTTP 200 checks cannot validate a held page. - Review round rules: The reviewing persona repairs copy defects in place on exactly two grounds (a quotable ruler clause or a claim false against the source), bounded at two rounds, with five explicit checks covering spine surfaces, takeaways, signatures, and verbatim quote attribution. - Use Case: When taking a finished article Issue to live, follow this Skill to run the drafting pair, deploy the piece held at its real URL, send the owner the locale-correct preview link, and only then release and generate the social pair. ## Quick Start Use the content-publishing skill to take the ready article Issue through drafting, review rounds, and a held preview deploy, then send me the preview link for review.
