SOCIAL

One pillar piece into a month of posts

Use when you need a month of social from a single substantial article without repeating the same point weekly.

pillar-to-month-calendar.md

Download .md

You are planning {{DAYS}} days of social posts from one pillar article, for {{PLATFORM}}, audience {{AUDIENCE}}.

Pillar article:
"""
{{ARTICLE_TEXT}}
"""

Posting cadence: {{POSTS_PER_WEEK}} posts per week.

Output a table: Day | Angle | Post type | Hook line | Core point | Link? (yes/no) | Source section of the article.

Rules for the plan:
- Every row must draw on a different section or claim of the article. If the article does not contain enough distinct claims to fill the calendar, stop and say how many days it honestly supports.
- Post types must vary across: opinion, how-to, mistake teardown, short case, question to audience, data point, behind the process, myth correction. No type more than twice a week.
- No more than one in three posts carries the link.
- Hook lines must be final copy, not descriptions.
- Do not invent examples, clients, or figures that are not in the article. Mark any gap as [NEEDS INPUT: what you need from me].

After the table, list the three angles you would cut first if the month had to shrink, and why they are weakest.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{DAYS}}
{{PLATFORM}}
{{AUDIENCE}}
{{ARTICLE_TEXT}}
{{POSTS_PER_WEEK}}

Getting a better result

Ask it first how many days the article honestly supports, then set the calendar to that number.
Fill the [NEEDS INPUT] rows yourself - those are the posts with your actual experience in them, which usually perform best.
Keep the source-section column so you can tell at a glance when you are recycling the same third of the article.

Questions about this prompt

When do I need a calendar rather than planning week by week?

When one article has to carry {{DAYS}} days of posting and you want to know in advance where it runs out. Week by week planning hides the repetition until you are three weeks in and posting the same point in different words. Use this before you commit to a cadence, not after.

What do I need ready?

The full pillar text, the platform, a day count and a real figure for {{POSTS_PER_WEEK}}. The tips suggest asking first how many days the article honestly supports and setting {{DAYS}} to that answer, which beats setting thirty and watching it stretch the final week over material that was never there.

What comes back, and which column earns its place?

A table with a final-copy hook line per row and a source-section column, then the three angles it would cut first. The source-section column is the one that pays off over a month: it shows at a glance when three consecutive posts come from the same third of the article, which readers notice before you do.

What is the mistake?

Deleting the [NEEDS INPUT] rows because they look unfinished. Those are the posts asking for your own examples, and they carry experience the article cannot supply. Filling them is slower than dropping them and is usually where the month's strongest post comes from, as the tips say.