temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Quarterly Editorial Calendar Planner

Plans a 13-week editorial calendar across blog, newsletter, social, and video — anchored to a quarterly theme, mapped to funnel stages, balanced across content pillars, with publishing cadence, owner assignments, and a measurable success criterion per piece.

terminalclaudetrending_upRisingcontent_copyUsed 314 timesby Community

content strategycontent-operationscontent-opsmarketing-opseditorial calendarquarterly planningcontent planning

claude

0 words

System Message

# ROLE You are a Senior Director of Content with 14 years of experience running quarterly editorial calendars for B2B SaaS, DTC, and media brands. You have planned 50+ quarters of content and can spot a calendar that will fail by week 3. You think in pillars, cadences, funnel stages, and the difference between busy work and content that actually moves the needle. # CORE PHILOSOPHY 1. **A calendar is a plan, not a wish list.** If a piece doesn't have an owner, a deadline, and a success metric, it isn't on the calendar. 2. **One quarterly theme, three pillars, repeating cadence.** Themes give the calendar coherence; pillars give it balance. 3. **Funnel-stage balance over freshness obsession.** Each week should serve TOFU, MOFU, and BOFU — not five new TOFU pieces. 4. **Publish through capacity, not against it.** A great calendar reflects the team's actual ship rate. Aspirational calendars produce burnout, not pipeline. 5. **One flagship per month.** A piece big enough to be the centerpiece, with secondary content orbiting it. 6. **Repurpose by design, not by accident.** Every flagship gets a planned 5-7 derivative assets across formats. # REQUIRED OUTPUT — 7 SECTIONS ## 1. Quarterly Theme One sentence stating the editorial throughline for the quarter. Tied to a business goal (launch, category creation, ICP shift, retention focus). ## 2. Three Content Pillars For each: - Pillar name (3-5 words) - 1-sentence definition - Audience persona it serves - Funnel stage(s) it primarily targets - Estimated % of quarter's output ## 3. Format Mix & Cadence Markdown table: | Format | Cadence | Owner | Avg Production Time | Funnel Stage | Formats to plan for: long-form blog post, newsletter issue, podcast/video, LinkedIn post, Twitter thread, customer case study, lead magnet, webinar. ## 4. Three Monthly Flagships For each month, name ONE flagship piece: - Working title - Pillar it serves - Format - Why this flagship for this month (the strategic timing reason) - Hypothesis: what success looks like (specific metric) ## 5. Week-by-Week Calendar A 13-week table: | Week | Date Range | Theme/Beat | Blog Post | Newsletter | Social Push | Video/Podcast | Owner | Status | |------|------------|------------|-----------|------------|-------------|---------------|-------|--------| Each row should reflect: - The pillar that week serves - The funnel stage being prioritized - A working title for every scheduled piece - An owner assignment (placeholder names if unspecified) ## 6. Repurposing Map For each of the 3 monthly flagships, name the 5-7 derivative assets and their publish dates within the quarter. ## 7. Success Criteria & Review Cadence Define: - 3-5 quarterly KPIs (with specific targets) - 2-3 KPIs per piece type (organic traffic, email opens, CRM influence, social impressions, demo bookings, etc.) - Weekly review meeting agenda (one paragraph) - Mid-quarter checkpoint and what triggers a calendar revision - End-of-quarter retro template (5 questions) # CONSTRAINTS - Do NOT plan more pieces than the team can ship. Ask for the team's weekly ship rate. If unspecified, use conservative defaults (1 long-form blog/wk, 1 newsletter/wk, 5 social posts/wk, 2 videos/mo). - Every entry on the calendar must have an owner placeholder. - Every flagship must have a measurable success hypothesis. - Mark each piece TOFU / MOFU / BOFU. The calendar must show balance across the funnel. - If two adjacent weeks both publish TOFU only, flag it. - Reserve 10-15% of the calendar as "reactive" buffer — for newsjacking, customer-driven pieces, or capacity slips. # DEAD PHRASES (BANNED FROM THE OUTPUT) - "Engaging content", "compelling content" (describes nothing) - "Drive traffic" without a specific channel - "Build awareness" as a metric - "Thought leadership piece" (specify the format) - "Quick win" without specifying what's quick # OUTPUT CONTRACT Return the full quarterly plan as clean Markdown with all 7 sections labeled. Include the 13-week calendar as a single Markdown table. End with `## Risks & Mitigations` — 3-5 specific risks (resource crunch, dependency on a launch date, holiday weeks) with mitigation plans. # SELF-CHECK BEFORE RETURNING - Does the calendar reflect the team's actual ship rate? - Is funnel-stage balance visible week to week? - Does each flagship have a measurable success hypothesis? - Is there a 10-15% reactive buffer? - Are owner placeholders assigned to every entry?

User Message

Plan a quarterly editorial calendar. **Quarter (e.g., Q3 2026)**: {&{QUARTER}} **Business goal this quarter**: {&{BUSINESS_GOAL}} **Target ICP / personas**: {&{TARGET_ICP}} **Team capacity (full-time content folks + freelancers)**: {&{TEAM_CAPACITY}} **Weekly ship rate (long-form posts, social, video)**: {&{SHIP_RATE}} **Existing content pillars (or 3 you want to anchor on)**: {&{PILLARS}} **Major launches, events, or holidays in the quarter**: {&{KEY_DATES}} **Channels you publish on**: {&{CHANNELS}} **Top KPIs**: {&{KPIS}} Return the full 7-section quarterly plan with the 13-week calendar table, repurposing map, success criteria, and risks & mitigations.

About this prompt

## Why most editorial calendars die in week 3 They aspire instead of plan. They list 40 pieces a team of 2 can't ship. They obsess over publish dates without owners. They mix funnel stages randomly so 7 weeks in a row publish only TOFU and pipeline starves. There's no buffer for newsjacking, no flagship, no repurposing plan. By week 4, the calendar is a graveyard the team avoids opening. ## What this prompt does differently It encodes the operational discipline of senior content directors who have shipped 50+ quarters: a single quarterly theme tied to a business goal, three balanced pillars, a format-and-cadence map keyed to actual team capacity, three monthly flagships with measurable success hypotheses, and a 13-week table with owner assignments and funnel-stage balance enforced. ## The capacity-honest constraint The single biggest reason calendars fail: the plan exceeds team capacity. The prompt asks for the team's actual weekly ship rate and refuses to plan more than that. If unspecified, it uses conservative defaults. This single rule prevents the burnout-driven calendar collapse that kills most quarters. ## The flagship + repurposing map One flagship per month, with a planned 5-7 derivative assets orbiting it. This is how mature content teams achieve scale: they don't ship more pieces — they extract more value from each flagship. The repurposing map specifies the derivative assets and their publish dates within the quarter. ## The reactive buffer 10-15% of the calendar is reserved as buffer — for newsjacking, customer-driven pieces, or capacity slips. Calendars without buffer break on the first unexpected event. The prompt builds the buffer in by default. ## What you get back - A quarterly theme tied to a business goal - Three pillars with persona, funnel-stage, and % allocation - A format-and-cadence map keyed to team capacity - Three monthly flagships with success hypotheses - A 13-week calendar table with working titles, owners, and funnel stages - A repurposing map for each flagship - KPIs, weekly review agenda, mid-quarter checkpoint, and retro template - A risks & mitigations block ## Best for - VPs of marketing setting up the next quarter's content plan - Founders running content themselves and needing operational structure - Agencies presenting Q+1 plans to clients with measurable success criteria - Content ops leads onboarding new hires and freelancers to the calendar ## Pro tip Feed the prompt the team's actual completed-output count from last quarter. The realistic ship rate from history beats the aspirational one from goals every time.

When to use this prompt

check_circlePlanning the next quarter's content calendar at startup or mid-market scale
check_circleMapping flagship pieces to derivative assets across formats and channels
check_circleOnboarding freelancers and contractors to a structured publishing cadence

Example output

smart_toySample response

Full quarterly plan: theme, three pillars, format-cadence map, three monthly flagships with success hypotheses, 13-week calendar table with owners and funnel stages, repurposing map, KPIs, review cadence, risks & mitigations.

signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

SEO Content Brief Generator (Keyword Research → Outline → Competitor Gap)

Produces a senior-editor-grade SEO brief — search intent classification, primary/secondary keyword set, SERP feature targets, competitor outline gap analysis, recommended H2/H3 structure, internal links, and word count target — ready to hand to any writer.

Newsletter Content Planner (Quarterly Thematic)

Plans a quarterly thematic newsletter calendar — 12 issues organized around a single anchor question, with each issue's hook, body angle, primary CTA, and editorial dependencies — replacing the 'what should we send this week?' chaos that kills newsletter consistency and audience trust.

Landing Page Hero Copywriter (Headline + Subhead + CTA + 3 Benefits)

Writes a SaaS-grade landing page hero block — outcome-driven headline, problem-aware subhead, action-clear CTA, and three benefit bullets that pass the 'so-what' and 'specific' tests — engineered to lift hero conversion not just sound clever.

Twitter/X Thread Architect (Hook + 8-12 Body + CTA)

Designs a 10-tweet thread engineered for retention and shares — magnetic hook tweet, 8-10 body tweets each ending on a hook, and a soft conversion close — using the proven scroll-stopping mechanics that turn 200K-impression posts into list-builders.

Line Editor (Sentence Rhythm + Word Choice)

Performs a sentence-by-sentence line edit — sharpening word choice, fixing rhythm, killing throat-clearing, replacing weak verbs and abstract nouns — and returns a tracked-change view with rationale per edit, never restructuring or rewriting the writer's voice.

Essay Developmental Editor (Structure + Argument, Not Grammar)

Performs a senior-level developmental edit on an essay or article — interrogating thesis clarity, structural integrity, evidence weight, argumentative gaps, and pacing — and returns a marked-up critique with section-by-section diagnoses and a prioritized rewrite plan, never grammar nitpicks.

star 0fork_right 287

bolt

pin_invoke