Founder content rhythm

skills/founder-content-rhythm/SKILL.mdView on GitHub

This applies every week. It produces founder posts from the founder’s own material, so the founder edits instead of writing from nothing.

Before you start

This skill works on its own. If the person has their own marketing brain (or any folder of context files about their company), read the files listed under reads in the header first and cite them for every fact. If they do not have one, do not look for one: ask for the two or three facts this play needs and go on. Never invent a fact; a blank is a question for the person.

Tools: this play speaks in verbs (check the CRM, pull the call, schedule the post). TOOLS.md at the root of this repo lists the tools recommended for each verb. The company’s own 1-context/stack.md wins when it exists. No tool is required; a spreadsheet and a mail client cover most of it.

The play

1. Read the context (see Before you start) and the founder section of 2-standards/brand-voice.md (themes, cadence, meeting days).
2. Before the content meeting: scan the founder’s own calls, inbox and chat for the week (on the founder’s account where the tools allow). Pull five to eight moments: a customer question, a shop visit, a conference exchange, a number someone said, a disagreement. For each, one line and a prompting question (“what did you tell them?”).
3. In the content meeting: the founder picks and adds; each pick becomes an entry in content-calendar with the theme and the story.
4. Draft through founder-voice: one point per post, the story first, the lesson cut. Clear any customer or claim through permission-check.
5. Before the review meeting: finalize drafts; the founder edits or rejects. Rejected drafts go back with the reason noted for next week’s scan.
6. After review: schedule-post for the following week on the founder’s days.
7. Track weekly: ideas surfaced, drafts accepted, posts published. If accepted drafts fall below half, the scan is pulling the wrong material; adjust the themes.

What good looks like

• The best operator brings the founder their own week back as prompts. Founders will edit a draft built on something they said; they will not write from a blank page.
• The mediocre version ghostwrites generic thought leadership and the founder stops reading the drafts.
• Good output is a weekly meeting that takes 30 minutes because the ideas arrived with the founder’s own words attached.

Rules

• MUST source ideas from the founder’s own material, not from industry news alone.
• MUST get the founder’s review before scheduling.
• NEVER invent a story or a quote for the founder.
• NEVER schedule a founder post that names a customer without permission-check.