## TL;DR

A one-agent content calendar is a weekly template, not a campaign plan: one anchor piece, two derivatives, and daily lightweight presence, repeating. Pick theme days, cap the output at what one run can produce, and protect a buffer week monthly. Consistency at a sustainable pace beats ambitious calendars that collapse by week three.

```text
content calendar for a one-agent marketing team
```

## Use this when

- Planning content as a solo operator or single agent
- Cadence keeps slipping
- You need a repeatable weekly shape

## Not for this skill when

- You have a team (use a real editorial process)
- Output is event-driven, not cadence-driven (plan around events)
- You cannot sustain even a light cadence (go lighter, not zero)

## Steps

1. Fix the weekly shape. One anchor piece (article or skill), two derivatives (thread, snippet), and lightweight daily presence. Expected: a template you can fill in 30 minutes.

2. Assign theme days. Monday anchor draft, Wednesday derivatives, Friday scheduling and review, for example. Expected: every weekday has a job.

```
weekly template:
  mon: draft anchor piece
  tue: finish + review anchor
  wed: two derivatives from anchor
  thu: light presence, replies
  fri: schedule next week, review metrics
```

3. Cap output at production reality. If one anchor plus two derivatives is the max, that is the calendar; ambition beyond capacity just creates backlog guilt. Expected: a calendar you actually complete.

4. Keep a backlog, not a backlog crisis. Ideas go in a list, ranked; the calendar pulls from the top. Expected: never staring at a blank week.

5. Review monthly, adjust quarterly. What got engagement, what flopped, what to drop. Expected: the calendar evolves with evidence.

## Variant phrasings

### solo content calendar template

Weekly shape: anchor, derivatives, daily presence. Theme days, capped output.

### planning content as a one-person team

Repeatable weekly template beats campaign thinking; protect a buffer week.

### sustainable content cadence

Cap at what you can produce weekly, backlog the rest, review monthly.

## Why it happens

Solo content fails from over-planning, not under-planning: an ambitious calendar collapses, then nothing ships for a month. A modest repeating template ships every week, and shipping every week compounds.

## Edge cases / pitfalls

- Buffer weeks are not laziness; launches and incidents will eat a week eventually.
- Do not fill every slot; white space absorbs the weeks reality intrudes.
- Theme days beat task lists; "Wednesday is derivatives day" survives busy weeks.
- If the anchor slips, ship the derivatives anyway; momentum matters more than completeness.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_7WzLL1kxcMqBsfJcmsuC3A