name: content-publishing-rhythm-runner description: > Runs the full weekly content publishing cadence — topic selection, thought leadership post drafting, optional repurposing for a secondary channel, and content log update. Every Tuesday morning. 45 minutes. metadata: author: "Kathryn Brown, Practice Builders" version: "1.0.0" date: "2026-04-28" sop: "Content Publishing Rhythm" category: "Content & Visibility" frequency: "Weekly" estimated-time: "45 min" trigger: "Every Tuesday morning"

Content Publishing Rhythm — Runner

You are executing the Content Publishing Rhythm SOP for an independent consultant. Without a fixed publishing cadence, content becomes reactive — you post when inspired and go dark when client work peaks. This runner converts thought leadership into a standing weekly output that runs regardless of how the rest of the week looks.

Do not skip steps. Do not ask questions across multiple turns — collect everything upfront.

What you'll have when this is done: One published thought leadership post, and where applicable one repurposed derivative piece scheduled on a secondary channel — both logged in your content tracker with publish date. Your Tuesday cadence has held.

Step 1: Collect Your Inputs

Ask the user for the following (all at once, in a single prompt):

This Week's Topic:

• A topic, insight, or observation from current client work, a prospect question, or a recent engagement pattern
• If the topic came from a client situation: enough detail to build anonymized examples (situation, behavior, consequence — for at least two examples)
• If the queue is empty: what happened in your work this week that surprised you, confirmed a pattern, or made you think "people don't realize this"

Audience and Platform:

• Target audience for this post (e.g., "consulting firm owners," "RIAs managing \$50M-\$200M")
• Primary publishing platform (LinkedIn, blog, newsletter)
• Secondary platform for repurposing (if applicable — e.g., "also want a short email version")

Content Log Context:

• Topics from the last 4 weeks of published posts (titles or brief descriptions) — to avoid repeating themes
• Any themes you've been meaning to cover but haven't yet

Voice and Positioning:

• How you want to come across (e.g., "peer sharing a pattern," "experienced operator naming what others miss")
• Anything to avoid (e.g., "don't reference financial planning specifically," "stay away from anything that sounds like coaching")

If the user doesn't provide content log history, proceed and note that theme-overlap checking is limited.

Step 2: Select and Validate the Topic

Review the inputs against the content log.

Topic validation:

• Does this topic overlap with anything published in the last 4 weeks? If yes, find a distinct angle or ask the user for an alternative.
• Is the topic specific enough to build a post around? "Client communication" is too broad. "Why the best consultants send fewer status updates" is specific. Sharpen if needed.
• Does the topic contain a pattern (something recurring across clients) or a contrarian angle (something the audience believes that's wrong or incomplete)? If neither, probe: "What would a peer disagree with you about here?"

Confirm: State the topic in one sentence using this format: "[Audience] keeps [doing X] because [reason], and it's costing them [consequence]." If the input doesn't fit this format cleanly, state the core insight in your own sentence and flag which element (audience, behavior, reason, or consequence) is weakest.

Step 3: Draft the Thought Leadership Post

Using the validated topic, audience, and platform from Steps 1-2, write the complete post.

3A. Insight Extraction

Before writing, answer three questions:

• The pattern in one sentence: What keeps happening across clients? Force it into the format above if not already done.
• Why it's invisible: Why don't the people experiencing this pattern see it? What makes it hard to spot from the inside?
• The contrarian angle: What do you believe about this that most people in your space don't say? This is the edge that makes the post worth reading.

3B. Evidence Building

Take each client example from the input and anonymize:

• Change names, industries, and identifying details
• Preserve the structural truth: the situation, the behavior, the consequence
• Frame each example in 3-5 sentences

Anonymization test: Could the actual client read this and recognize themselves? If yes, abstract further. Could someone in the target audience read this and think "that's me"? If yes, the anonymization is right.

Build two example blocks, each 3-5 sentences.

3C. Post Assembly

Build the post using this structure:

Hook (1-2 sentences): Name the pattern. Best formats:

• Counterintuitive observation: "The consultants who bill the most hours are often the least profitable."
• Named problem: "There's a specific behavior I see in every firm I work with. I call it [name]."
• Pattern recognition: "Three clients this quarter. Same problem. None of them saw it coming."

Pattern description (3-4 sentences): Describe what you're seeing without judgment. Pure observation. This builds credibility.

Example 1 (3-5 sentences): First anonymized client story. Situation, behavior, consequence.

Example 2 (3-5 sentences): Second anonymized client story. Different context, same pattern. Two examples prove it's a pattern, not an anecdote.

The insight (2-3 sentences): Your point of view on why this happens and what it means. This is where the contrarian angle lives. "The real problem isn't [obvious thing]. It's [deeper thing]."

The shift (2-3 sentences): What changes when someone recognizes this pattern. Not a sales pitch — what became possible when the light went on.

Close (1-2 sentences): A specific question that invites engagement. Not "what do you think?" — something precise: "What's the pattern you keep seeing that nobody in your industry talks about?"

Total: 600-900 words.

3D. Headlines and Metadata

Generate:

• 3 headline options — each under 80 characters. One names the pattern directly, one uses a number or specific claim, one asks a question.
• One-sentence summary — what this post argues in one sentence.
• Platform recommendation — LinkedIn (default for B2B professional services), blog, newsletter, or cross-post with modifications.

Step 4: Edit for Voice and Accuracy

Review the draft against these checks:

• Voice match: Does the post sound like the user described in Step 1, not like a generic consultant?
• Anonymization: Could any client recognize themselves? If yes, abstract further.
• Advisory vs. operational: Remove anything that sounds prescriptive ("you should do X"). Replace with observational ("what I've seen work is X"). You're sharing a pattern, not a prescription.
• No pitch: Remove any overt selling, self-promotion, or calls to "book a call."
• Pattern-first opening: Does the post open with an observation, not "I" or "As a consultant"?
• Contrarian edge: Does the post say something a reasonable person in the same field might disagree with?
• Evidence quality: Do the examples actually prove the pattern, or just loosely illustrate it?

If any check fails, rewrite the weak section before proceeding.

Step 5: Repurpose for Secondary Channel (If Applicable)

If the user specified a secondary platform in Step 1, repurpose the finalized post. If no secondary platform was requested, skip to Step 6.

5A. Decompose the Post

Identify the standalone elements:

Tag each element:

• Insights: Strong (makes the reader stop), moderate (useful but familiar), weak (needs context)
• Stories: Self-contained or context-dependent
• Data points: Citable (source-backed) or experiential (from practice)
• Quotes: Memorable single sentences that stand alone

5B. Write the Platform-Native Draft

Select the strongest standalone element for the target secondary platform and write a complete draft using these platform norms:

LinkedIn: 150-300 words, first line is the hook, whitespace between paragraphs, professional first-person voice.

Twitter/X: Under 280 characters for singles, 3-7 tweets for threads. Punchy, direct.

Email: 200-400 words, conversational, personal, colleague-to-colleague.

Community (Slack, Circle): Short intro + question, under 150 words, peer-level.

Blog: 500-1000 words, structured with headers, authority voice.

The repurposed piece must stand completely on its own. No "as I wrote in my newsletter" — the reader doesn't know the original exists. Extract and develop, don't compress.

5C. Schedule

The repurposed piece goes on the secondary channel later in the week — stagger, don't stack. Recommend a specific day (e.g., "Publish Thursday" if the primary goes out Tuesday).

Step 6: Assemble the Final Output

Combine all outputs into a single document:

# Content Publishing Rhythm — Week of [Date]

## Primary Post

**Platform:** [Platform]
**Publish date:** [Tuesday date]
**Topic:** [One-sentence summary]

### Headline Options
1. [Option 1 — names the pattern]
2. [Option 2 — uses a number or claim]
3. [Option 3 — asks a question]

### Post Draft

[Complete 600-900 word post]

---

## Repurposed Piece (if applicable)

**Platform:** [Secondary platform]
**Scheduled date:** [Later in the week]
**Element used:** [Which element from the primary post]
**Format:** [LinkedIn / Tweet / Email / etc.]

[Complete platform-native draft]

---

## Content Log Entry

| Date | Topic | Format | Platform | Repurposed? | Secondary Platform | Secondary Date |
|------|-------|--------|----------|-------------|--------------------|----------------|
| [Date] | [Topic summary] | [Post type] | [Platform] | [Yes/No] | [Platform or —] | [Date or —] |

## SOPs to Trigger
- [ ] Newsletter Production SOP — if this week's topic feeds into a longer newsletter piece

Quality Check (Internal — never shown to the user)

Before presenting the output, verify:

Identify the weakest section. Rewrite it. Verify the rewrite is present and improved before presenting.

Rules

From the SOP:

• Don't wait for a "big enough" insight. The posts that land are small operational observations — patterns you're already seeing in client work. Publish the specific, timely thing over the polished, eventually-ready one.
• Don't skip repurposing when capacity is tight. Repurposing an existing post takes a fraction of the time writing a new one does. When the week is full, the Content Repurposer is how the cadence holds without sacrificing visibility.

From the Thought Leadership Post Writer skill:

1. Never open with "I" or "As a consultant." Open with the pattern. The reader's problem comes first.
2. Always use at least two client examples. One example is an anecdote. Two examples are a pattern.
3. Never name clients, even with permission. Anonymized examples are more powerful because readers project their own situation.
4. Keep the post between 600-900 words. Under 600 feels thin. Over 900 loses the LinkedIn audience.
5. Never end with a self-promotional CTA. End with a question that invites conversation.
6. Include a specific, nameable pattern or framework when possible. "I call this the [Name] problem" gives readers language for something they've felt but couldn't articulate.
7. Lead with the pattern, not the opinion. "Here's what I keep seeing" earns readers. "I believe" loses them.

From the Content Repurposer skill:

1. Never repurpose by summarizing. Extract one element and develop it as a standalone piece.
2. Each platform piece must stand alone. No references to the original — the reader doesn't know it exists.
3. Respect platform norms. A 500-word LinkedIn post is acceptable. A 500-word tweet thread is not.
4. Don't repurpose everything. Some elements are context-dependent. Flag them and skip.
5. Vary the hook and angle across pieces. People who follow you on multiple platforms will notice duplicate openings.
6. Track which repurposed pieces outperform the original. That data shapes your next original piece.

Output format:

• This is a Tuesday morning production document. Keep it scannable — short paragraphs, tables for structured data, bold for emphasis.
• Escape dollar signs as \$ for Notion compatibility.
• Present as a single unified document, not separate skill outputs.

Copyright (c) 2026 Kathryn Brown, Practice Builders Licensed under the Practice Builders Skill License v1.0 See https://practicebuilders.ai/license for terms.

This skill is part of the Consulting Practice SOP Manual, a Practice Builders product. Redistribution, resale, or derivative use without written permission is prohibited.