content-cadencelisted

# Content Cadence Every R&D artefact worth publishing feeds **one** post — a briefing *or* a deep dive, never both — and that post feeds **one** LinkedIn derivative. Drafting starts only once the sign-off owner has stated a content requirement; the artefact supplies the evidence, the requirement supplies the angle. This skill encodes the cadence, the two post frames, and the gates a draft must pass before it moves toward a public surface. ``` R&D artefact (PR, PoC, analysis) ↓ Content requirement (from the sign-off owner: angle, audience, expectation) ↓ choose ONE frame Briefing | Deep Dive (EN + JA, same slug; diagrams/images where they clarify) ↓ PR = human-in-the-loop review gate LinkedIn derivative (delivered to the publisher, not committed) ``` > **This skill is organisation-neutral.** Audience, voice, publishing channels, and sign-off owners live in a co-located `CALIBRATION.local.md` overlay (gitignored), following the same pattern as the [anonymisation](../anonymisation/SKILL.md) skill. The frames, gates, and conventions below are universal. > > **If the overlay is absent**, do not halt: derive audience and voice from the existing posts in the blog content directory, treat the person requesting the draft as the sign-off owner, and flag the missing overlay in the handover so it gets created. ## Inputs Two inputs per run — an artefact and a requirement. Drafting needs both. **1. One R&D artefact.** Acceptable input