make-content

What you get

One of five things, saved to the brand's workspace and shown in chat:

A repurposed set. One finished asset is mined into scored units. Each platform the brand uses gets a native version with a different lead unit and hook, ready to paste. Each version has an asset line saying what visual it needs and who makes it.
A single post. One LinkedIn, X, Threads or Instagram post, a thread, or an X long post or Article (references/formats.md), written native to its platform. It skips the calendar and the units table unless there is a source asset.
A fresh piece. A one-page brief, then a first draft in the brand's (or a named author's) voice. Long-form adds the publish kit: headline options, meta, slug, H2 skeleton, internal links, CTA, image notes and distribution notes.
A refresh redline. An old piece rewritten where it decays, with each change and its reason.
This week's newsletter issue, written from a saved template and the week's notes.

Every piece carries an edit note and a claims check: what was kept, softened and cut, and the proof that would restore each cut. The formats are listed in references/formats.md. Anything else is routed (Out of scope).

Before you start

Read research/market/positioning-<product>.md when present, else research/market/positioning.md, and its dated report. Carry the owner-selected launch direction into this work even when the live site/kit still uses earlier messaging. Unselected options stay proposals and every factual claim keeps its existing proof/approval status.

Briefs only, one or several topics: after the shared setup and evidence read below, run the existing make-content-content-brief skill (../make-content-content-brief/SKILL.md) for each supplied topic. Reuse a shared inventory/source read, distinguish overlapping intents, and deliver the requested briefs with their sources and proof gaps. Stop at briefs: no draft articles, outline-approval loop or newsletter intake unless asked. State any unfinished topic; never return one brief as a completed ten-topic request.