To run this task you must have the following required information:

> Time period (month or quarter), content pillars, publishing cadence, team capacity, any planned campaigns or launches

If you don't have all of this information, exit here and respond asking for any extra information you require, and instructions to run this task again with ALL required information.

---

You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).

Add all steps to your todo list now and begin executing.

## Steps

1. [Read Editorial Calendar Planning]: Read the documentation in: `./skills/sauna/[skill_id]/references/marketing.content.editorial.md` (Calendar structure, cadence, production workflow)

2. [Read SEO Integration for Content Strategy]: Read the documentation in: `./skills/sauna/[skill_id]/references/marketing.content.seo.md` (Keyword assignment for calendar entries)

3. [Read Content Strategy Library]: Read the file at `./documents/marketing/content/strategy.yaml` and analyze its contents (Check for existing pillars, audit gaps, and audience mapping)

4. Gather calendar context:
- What time period? (Next month, next quarter)
- What's the publishing cadence? (X blog posts/month, Y social posts/week)
- What pillars are we working with? (Check strategy file)
- Any campaigns, launches, or events to build around?
- Who creates content? (In-house, contractors, both)
- What's the realistic capacity?

If prior recipes have been run (Pillars, Audit, Map), reference their outputs:
- Use pillar definitions for topic alignment
- Use audit gap analysis for content priorities
- Use audience map for persona targeting

Be honest about capacity—an overambitious calendar breeds guilt, not content.


5. Calculate realistic capacity:

```markdown
## Capacity Assessment

**Available resources:**
- Writers: [X people, Y hours/week each]
- Designers: [X people, Y hours/week]
- Other: [Video, etc.]

**Effort estimates:**
- Blog post: [X hours writing + Y hours design]
- Social posts: [X hours/week]
- Newsletter: [X hours/edition]
- Other formats: [Estimates]

**Sustainable output:**
- Blog posts per month: [X]
- Social posts per week: [Y]
- Newsletters per month: [Z]

**Buffer reserved:** 20-30% for unplanned/reactive content
```

Ground the calendar in reality before planning.


6. Identify tentpole content first:

Start with the big pieces that anchor the calendar:
- Major campaigns or product launches
- Seasonal/timely topics
- High-effort cornerstone pieces
- Events (webinars, conferences)
- Industry moments (conferences, annual events)

```markdown
## Tentpole Content

| Date | Tentpole | Type | Lead Time Needed |
|------|----------|------|------------------|
| [Date] | [Product launch] | Campaign | 4 weeks |
| [Date] | [Annual guide] | Cornerstone | 6 weeks |
| [Date] | [Webinar] | Event | 3 weeks |
```

These anchor the calendar. Everything else fills in around them.


7. Generate the editorial calendar overview and first week:

```markdown
# Editorial Calendar: [Month/Quarter]

## Overview
- **Period:** [Dates]
- **Total blog posts planned:** [Number]
- **Total social posts planned:** [Number]
- **Pillar distribution:**
  - [Pillar 1]: [X] posts ([Y]%)
  - [Pillar 2]: [X] posts ([Y]%)
- **Tentpole content:** [List major pieces]

---

## Week 1: [Dates]

### Blog Content
| Pub Date | Title/Topic | Pillar | Target Keyword | Audience | Stage | Owner | Status |
|----------|-------------|--------|----------------|----------|-------|-------|--------|
| [Date] | [Topic] | [Pillar] | [Keyword] | [Persona] | TOFU | [TBD] | Planned |
```

Include specific dates. Add a target keyword for each blog post to ensure SEO alignment.


8. Continue the calendar with social content and asset tracking:

```markdown
### Social Content (Week 1)
| Date | Platform | Content | Linked To | Owner |
|------|----------|---------|-----------|-------|
| [Mon] | LinkedIn | [Post topic] | [Blog or standalone] | [TBD] |
| [Tue] | Twitter | [Thread] | [Blog title] | [TBD] |
| [Wed] | LinkedIn | [Post] | Standalone | [TBD] |

### Assets Needed (Week 1)
| Content | Assets Required | Design Owner | Due Date |
|---------|-----------------|--------------|----------|
| [Blog title] | Hero image, screenshots | [TBD] | [Date] |

## Week 2-4: [Continue same structure]
```

Track social content explicitly, not as afterthought. Continue for all weeks in the period.


9. Create content brief template and requirements:

```markdown
## Content Brief Template

For each blog post, complete before writing:

### [Content Title]
- **Target audience:** [Persona]
- **Funnel stage:** [TOFU/MOFU/BOFU]
- **Primary keyword:** [Keyword] ([X] monthly searches)
- **Secondary keywords:** [List]
- **Search intent:** [Informational/Commercial/etc.]
- **Outline:**
  - H2: [Section]
  - H2: [Section]
  - H2: [Section]
- **Key points to cover:** [Must-include information]
- **Internal links to include:** [List 3-5 related posts]
- **CTA:** [What action should reader take?]
- **Success metrics:** [Pageviews target, conversion goal]

**Brief deadline:** [X days before draft due]
```


10. Plan repurposing for major content:

```markdown
## Repurposing Plan

For each blog post, plan derivative content:

### [Blog Post Title]
- **LinkedIn post:** Key insight as standalone post (Day 0)
- **Twitter thread:** 5-7 tweet thread with main points (Day 0)
- **Newsletter feature:** Summary + link (Next edition)
- **Quote graphics:** 2-3 pullquotes as images (Day 1-3)
- **LinkedIn follow-up:** Discussion prompt (Day 3)
- **Twitter follow-up:** Single tweet callback (Day 7)

### [Major Cornerstone Piece]
- All above, plus:
- **Slide deck:** Key visuals for sharing
- **Video summary:** 2-3 min explainer
- **Podcast mention:** Work into upcoming episode
```

A single blog post can yield 5-10 derivative pieces with planning.


11. Add distribution plan for tentpole content:

```markdown
## Distribution Plans

### [Tentpole Title 1]
- **Primary:** Blog publish [Date]
- **Email:** Dedicated send or newsletter feature [Date]
- **Social:**
  - LinkedIn: [Day 0, Day 3, Day 7]
  - Twitter: [Day 0 thread, Day 1, Day 5]
- **Internal:** Share in [Slack channel], notify sales team
- **Paid amplification:** [Budget, targeting if applicable]
- **Outreach:** [Influencers, partners to notify]

### [Tentpole Title 2]
[Same structure]
```


12. Add newsletter calendar (if applicable):

```markdown
## Newsletter Calendar

| Send Date | Edition | Featured Content | Exclusive Content | CTA |
|-----------|---------|------------------|-------------------|-----|
| [Date] | [#/Name] | [Blog post 1], [Blog post 2] | [Newsletter-only item] | [Primary CTA] |
| [Date] | [#/Name] | [Blog post 3], [Resource] | [Newsletter-only item] | [Primary CTA] |
```

Plan newsletter content alongside blog, not as afterthought.


13. Establish timeline and contingency:

```markdown
## Production Timeline

**Standard blog post timeline:**
- Brief due: [X] days before publish
- Draft due: [Y] days before publish
- Design assets due: [Z] days before publish
- Review/approval: [A] days before publish
- Final edits + scheduling: [B] days before publish

**Buffer policy:**
- 20% capacity unplanned for reactive content
- 1-week buffer between draft complete and publish
- Backup content: [2-3 evergreen pieces ready to slot in]

**If deadline slips:**
- Bump to next available slot
- Pull from buffer/evergreen backlog
- Reduce scope before rushing quality

**Escalation:** If [X] pieces slip, reassess calendar capacity
```

Offer to save the editorial calendar to `./documents/marketing/content/strategy.yaml`.

**Suggested next steps:**
- Execute calendar and track actual vs planned
- After 1-2 months, run Analyze Content Performance to measure what's working
- Quarterly: revisit pillars based on performance data