How to Plan a Month of Content with Claude + Notion

01 · INPUT BRIEF

Start with the inputs Claude cannot infer

A polished calendar can still be fiction. Claude cannot know your real production time, audience language, product facts, or blackout dates unless you provide them. Collect these six input groups before asking for ideas. If a required field is missing, the prompt later in this guide tells Claude to stop and ask.

02 · DESTINATION

Choose how the calendar will reach Notion

Pick the delivery path before planning so the output uses fields your destination can accept. Anthropic describes a Notion connector that can work with content available through the authorized connection. Notion also provides a hosted MCP option for supported AI clients. Both require connection and authorization. That authorization can let the connected client read or update content your user can access in the selected workspace. The destination preview in this guide is a Kabo operating rule—not a page-level permission boundary.

Anthropic: Notion connector for Claude ↗Notion Developers: connect an AI tool to Notion MCP ↗Notion Developers: MCP security best practices ↗

Notion Help: import data into Notion ↗

Use a small schema you can audit

Start with the properties below and add complexity only when a real workflow requires it. A Notion calendar view needs a date property. A content row being visible in that view does not mean the post is scheduled on a social platform.

Notion Help: calendar views ↗Notion Developers: tools supported by Notion MCP ↗

03 · MONTH ARCHITECTURE

Build anchors before you fill 30 dates

Generating one isolated idea for every day encourages repetition disguised by different titles. Instead, build a few evidence-backed anchors: a useful tutorial, point of view, workshop, experiment, or launch moment. Then derive narrower pieces that answer a different question or use a different depth and format.

1. 01

   Choose two to four pillars

   Each pillar should connect the monthly goal to source material you already have. Drop a pillar that is supported only by Claude's general knowledge.

2. 02

   Give every anchor a source and payoff

   Record the notes, transcript, question, example, or product fact behind it. Name what the audience can do or understand after consuming it.

3. 03

   Make derivatives earn their own row

   A derivative should change the question, evidence, depth, or action. Cropping the same claim into three aspect ratios is distribution work, not three ideas.

4. 04

   Reserve review and buffer time

   Add production estimates before dates are locked. Kabo's working rule is planned hours plus a buffer must fit inside available hours. The prompt defaults to a 20% buffer, but you can replace it with your own known margin.

If an anchor needs a stronger opening, use the observable patterns in Kabo's guide to what viral videos have in common. Treat those patterns as editing prompts—not a promise that the finished post will go viral.

04 · COPYABLE PROMPT

Use this prompt to build the month

Replace every bracketed field. The prompt separates planning from writing: it instructs Claude to audit the inputs, calculate the load, show the full month, and report QA issues. It treats a second, exact approval phrase as a review convention for one destination and row set.

You are helping me plan one month of creator content. Build a realistic editorial calendar from the information I provide. Do not invent audience research, analytics, customer quotes, product facts, platform rules, trends, deadlines, or performance predictions.

REQUIRED INPUTS
- Planning window: [START DATE] to [END DATE]
- Timezone: [TIMEZONE]
- Audience: [WHO THIS MONTH IS FOR]
- Primary platform: [PLATFORM]
- Secondary channels: [CHANNELS OR NONE]
- Monthly goal: [ONE GOAL]
- Allowed CTAs: [CTA OPTIONS, INCLUDING NONE]
- Content pillars: [2–4 PILLARS]
- Available source material: [NOTES, TRANSCRIPTS, COMMENTS, LINKS, PRODUCT FACTS]
- Available production hours: [HOURS]
- Effort by format: [FORMAT = HOURS]
- Blackout, launch, review, and approval dates: [DATES]
- Notion destination: [DATABASE NAME + URL/ID, OR "NO CONNECTOR"]
- Existing Notion properties: [PROPERTY NAMES + TYPES, OR "NEW DATABASE"]

STOP CONDITIONS
If the planning window, timezone, audience, primary platform, monthly goal, or production capacity is missing, stop and ask only for the missing information. If a source is missing for a factual claim, keep Status as "Idea," write "Needs evidence" in Notes, and do not fill the gap with a plausible statement.

PLANNING METHOD
1. Restate my constraints in a short input audit. Separate supplied facts from assumptions and unresolved questions.
2. Propose 2–4 content pillars. For each pillar, cite the supplied source material that supports it.
3. Choose a small set of anchor pieces before filling dates. Derive platform-specific follow-ups from each anchor, but give every derivative a different audience question, hook, depth, or next action.
4. Estimate production hours using my format estimates. Keep planned work inside capacity and preserve at least 20% of available time as buffer unless I provide a different rule.
5. Place anchors, derivatives, community posts, review days, launch moments, and buffers in a logical sequence. Respect blackout dates.
6. Use one Status vocabulary only: Idea, Planned, Approved, Drafting, Ready, Scheduled, Published. Put blockers such as missing evidence, pending audience replies, and blackout reasons in Notes rather than inventing extra status values. Do not treat a Notion calendar as a social publishing system.

PREVIEW OUTPUT
First return:
A. Input audit: supplied facts, missing information, and assumptions that need approval.
B. Capacity summary: available hours, planned hours, buffer hours, and the calculation.
C. Pillar and anchor map: pillar, anchor, derivatives, source/evidence, goal, and CTA.
D. A full calendar preview with one row per calendar item; dates may repeat across channels. Use these columns:
Publish date | Working title | Platform | Format | Pillar | Content role | Source / evidence | CTA | Effort hours | Status | Notes
E. A QA report covering capacity, audience fit, evidence, distinctness, repurpose quality, platform fit, goal/CTA, calendar logic, Notion safety, and state honesty.

NOTION WRITE GATE
Do not create, edit, or delete anything in Notion during the preview. After I review the preview, show:
- the exact workspace/database destination;
- existing property -> proposed property mapping;
- number of rows to create and rows to update;
- duplicate check and date/timezone check;
- any unsupported or uncertain field types.

Wait for the exact phrase APPROVE NOTION WRITE before making a Notion change. Approval applies only to the destination, mapping, and rows shown in the latest preview. If anything changes, preview it again.

NO-CONNECTOR FALLBACK
If no Notion connection is available, return the approved calendar as both a Markdown table and UTF-8 CSV using the same columns. In the CSV, format Publish date as MM/DD/YYYY with the full year so Notion can parse it as a date. State clearly that importing a CSV adds database rows; it is not automatic sync, upsert, scheduling, or social publishing.

05 · HUMAN REVIEW GATE

Check the plan before Claude writes to Notion

Read the calendar like an editor and a production manager. A pass means the plan is safe to place in the database—not that every post is finished, scheduled, or likely to perform.

1. 01

   Capacity

   Do planned production hours fit inside available hours after preserving a buffer?

2. 02

   Audience fit

   Can every publishable row name the same intended audience and a real question, need, or tension?

3. 03

   Evidence

   Does every factual or audience claim have a supplied source, or a visible hypothesis label?

4. 04

   Distinctness

   Are the hook, promise, and payoff meaningfully different from nearby rows?

5. 05

   Repurpose quality

   Does each derivative change the angle, depth, or delivery instead of copying the anchor?

6. 06

   Platform fit

   Is the format native to the named platform, with enough context to stand on its own?

7. 07

   Goal and CTA

   Does each CTA support the monthly goal, and are some rows allowed to teach without asking?

8. 08

   Calendar logic

   Do anchors precede derivatives, review days precede deadlines, and blackout days remain protected?

9. 09

   Notion safety

   Have you checked the destination, property mapping, row count, dates, and likely duplicates before writing?

10. 10

    State honesty

    Are planned, approved, scheduled, and published kept separate so a calendar never implies work is live when it is not?

06 · CONSTRUCTED EXAMPLE

See the workflow in a constructed 30-day month

Maya Chen is a fictional freelance-design educator with a fictional 18.4K Instagram audience and 2.7K newsletter list. She is launching a fictional client-onboarding mini-course and has 34 production hours for November 2026. None of the names, audience figures, time estimates, content results, or rows below describe a Kabo customer or provide a benchmark.

The plan uses four clusters instead of 30 unrelated prompts. Review and buffer days are visible, unsupported response-based posts stay on hold, and the final retrospective records what actually shipped. After the month, Maya would replace planned states with real outcomes rather than asking Claude to infer performance.

07 · SAME METHOD, DIFFERENT CLIENT

Use the Same Content-Planning Workflow in Codex

The editorial method does not change in Codex: provide the same input brief, use the same master prompt, require the same preview and QA report, then approve a specific Notion write—or keep the CSV fallback. There is no reason to regenerate the strategy just because the AI client changes.

To give Codex access to Notion, configure the Notion hosted MCP server in a supported local Codex environment that reads MCP configuration, then complete OAuth. OpenAI documents MCP configuration and OAuth support; Notion documents its hosted endpoint and supported tools. Access still follows the authenticated connection, so confirm the workspace and destination at the review gate.

OpenAI Developers: Model Context Protocol in Codex ↗Notion Developers: connect an AI tool to Notion MCP ↗Notion Developers: tools supported by Notion MCP ↗

08 · HANDOFF DIAGNOSIS

Troubleshoot the handoff to Notion

Notion Help: import data into Notion ↗Notion Help: calendar views ↗

09 · SOURCES AND METHOD

What is documented, and what is Kabo's method

Connector, MCP, authentication, supported-tool, import, and calendar-view statements come from the official sources below. The input brief, capacity envelope, anchor-to-derivative method, prompt, write gate, QA checklist, and Maya example are Kabo editorial material. Public creator workflows helped frame the question, but they do not prove a fixed time saving or content result and are not counted in the primary-source badge.

• Anthropic: Notion connector for Claude ↗
• Notion Developers: connect an AI tool to Notion MCP ↗
• Notion Developers: tools supported by Notion MCP ↗
• Notion Developers: MCP security best practices ↗
• Notion Help: import data into Notion ↗
• Notion Help: calendar views ↗
• OpenAI Developers: Model Context Protocol in Codex ↗