> ## Documentation Index
> Fetch the complete documentation index at: https://docs.depost.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Plan your content

> Build a week, a month, or a campaign, instead of deciding what to post each morning.

Planning in chat produces a set of posts that relate to each other, rather than a series of
unconnected ones. It's the difference between publishing consistently and publishing
coherently.

## What you can ask for

<CardGroup cols={2}>
  <Card title="A weekly plan" icon="calendar-days">
    The default. Enough to work from, short enough to change.
  </Card>

  <Card title="A monthly plan" icon="calendar-range">
    For a theme you want to develop rather than a week you want to fill.
  </Card>

  <Card title="A launch campaign" icon="rocket">
    A sequence building toward a date — before, during, after.
  </Card>

  <Card title="A lead magnet promotion" icon="magnet">
    Posts that drive people to something you're giving away.
  </Card>
</CardGroup>

Some prompts:

* *"Plan my week of content"*
* *"Build me a month of content around agentic workflows"*
* *"We launch on the 14th — plan the campaign around it"*
* *"Plan a week promoting my new guide without being repetitive about it"*

## What comes back

<Frame>
  <img src="https://statics.depost.ai/docs/chat/plan-weekly.png?v=2" alt="A weekly content plan in chat, showing the content mix as percentages, content pillars, and follow-up actions" />
</Frame>

A plan arrives with a stated focus, a **content mix** as percentages — education, proof,
conversion, story — and a set of **content pillars**, the recurring themes it rotates
between so the week doesn't repeat one angle.

Underneath are follow-ups that use the plan: create a post from the first day, turn a visual
day into a carousel, generate CTA options for a conversion day.

## Say what the plan is for

A plan built without a goal spreads evenly across everything, which is rarely what you
want. Name the outcome — authority in a niche, signups, hiring, a launch — and the mix
shifts to serve it.

Also say what's already fixed. If Tuesday is a case study you've committed to, say so and
the plan works around it rather than replacing it.

## From plan to posts

The plan is a starting point, not a schedule. Nothing is created until you ask.

<Steps>
  <Step title="Read it before drafting">
    Cut what doesn't fit. A plan you half-agree with produces posts you half-mean.
  </Step>

  <Step title="Draft them one at a time">
    *"Write the Tuesday one"*. Each draft carries the plan as context.
  </Step>

  <Step title="Put them on the calendar">
    Schedule from the editor, or into a queue slot. See
    [schedule or publish](/posts/schedule-or-publish).
  </Step>
</Steps>

<Tip>
  Say what's already fixed before asking. A plan that works around your committed Tuesday
  case study is usable; one that replaces it isn't.
</Tip>

## Related

<CardGroup cols={2}>
  <Card title="Your content strategy" icon="target" href="/chat/strategy">
    The profile that shapes every plan.
  </Card>

  <Card title="Analyze your content" icon="chart-line" href="/chat/analyze">
    What to build the plan on.
  </Card>

  <Card title="Calendar" icon="calendar" href="/calendar/overview">
    Where the plan becomes a schedule.
  </Card>

  <Card title="Create a post" icon="pencil" href="/chat/create-post">
    Turning a planned item into a draft.
  </Card>
</CardGroup>
