Transforms strategic campaign elements into a week-by-week execution timeline with themes, milestones, escalation patterns, and blog integration. Creates the temporal backbone that connects strategy to daily execution.

Recipe Name: RCP-004-002-012-TIMELINE-ARCH – Campaign Timeline Architect

RCP-005-001-005-TIMELINE-ARCH – Campaign Timeline Architect

Print Recipe Pin Recipe

Multi-Recipe Combo Stage Single Recipe

Recipe Category CFT-FWK-COOKBK-BRAND-ID – CRAFT Cookbook – Branding and Identity

Recipe Subcategory Blogging with A.I., Brainstorming with A.I.

Recipe Difficulty Easy

Recipe Tag: Foundational | Introduced in the POC

Requirements

Any AI Chat Platform (platform-agnostic recipe) Any of the following: Claude (Anthropic), ChatGPT (OpenAI), Gemini (Google), Grok (X.ai), Perplexity, Microsoft Copilot

How To Start

▢
STEP 1: Choose Your Format
Decide what you need:- Full catalog: "Show me all available recipes"- Quick list: "List recipes in compact format"- Single recipe: "Explain the TOKEN-MONITOR recipe"- Filtered view: "Show me Base Cookbook recipes only"
STEP 2: Review the Output
The AI generates your requested format with recipe descriptions, purposes, roles in CRAFT, and example usage. Use this as reference documentation or learning resource.

When to Use This Recipe

Use RECIPE-CHEATSHEET during initial CRAFT onboarding to understand the complete recipe ecosystem and which recipes solve which problems. Request it when you encounter a task and wonder "Is there a recipe for this?" to discover existing capabilities before creating custom solutions. Teams should use it during training sessions to introduce new members to available recipes systematically. Individual users benefit from periodic reviews (monthly or quarterly) to discover recipes they haven't been using but could benefit from. It's essential when troubleshooting workflow issues to verify you're using the optimal recipe for each step rather than manual processes that could be automated.

Recipe FAQ

Q1: What’s the difference between detailed and compact formats?

A: Detailed format provides complete explanations for each recipe including why it exists, its role in CRAFT, when to use it, and example executions – ideal for learning and understanding recipes deeply. Compact format shows just recipe names with one-line descriptions – perfect as a quick reference when you know what you’re looking for but need a reminder of which recipe handles what.

Q2: How do I find the right recipe for my specific task?

A: Start by describing your task naturally: “What recipe helps with X?” The AI will search the catalog and recommend appropriate recipes. Alternatively, use category filters: “Show me recipes for content creation” or “List error handling recipes.” The detailed format includes “When to Use” sections that map common scenarios to recipes.

Q3: What does “Why It’s CORE” mean for Base Cookbook recipes?

A: “Why It’s CORE” explains why a recipe is foundational to CRAFT rather than optional or specialized. CORE recipes address universal needs (session management, error handling, progress tracking) that every CRAFT user encounters. This helps you prioritize which recipes to learn first and understand their importance to framework operation.

Q4: Can I request information about recipes that don’t exist yet?

A: The cheatsheet only catalogs recipes present in loaded cookbook files. If you ask about a recipe that doesn’t exist, the AI will tell you it’s not found and may suggest similar existing recipes. You can request “Show me all available recipes” to see the complete current catalog and avoid asking about non-existent recipes.

Q5: How often should I review the recipe cheatsheet?

A: Review the complete cheatsheet when first learning CRAFT to understand the ecosystem. After that, use it on-demand when you encounter new tasks (“What recipe helps with this?”) or when cookbooks are updated with new recipes. Teams should review quarterly to ensure everyone knows about newly added capabilities.

Actual Recipe Code

(Copy This Plaintext Code To Use)

# =========================================================

# BEGIN RCP-004-002-012-TIMELINE-ARCH

# =========================================================

# RECIPE: BEGIN: CAMPAIGN-TIMELINE-ARCHITECT

# =========================================================

# Recipe ID: RCP-004-002-012-TIMELINE-ARCH-v1.00a

# Title: Campaign Timeline Architect

# Category: CAT-004-BRAND-IDENTITY

# Subcategory: SUBCAT-002-CAMPAIGN-PLANNING

# Layer: TACTICAL

# Version: 1.00a

# Created: November 25, 2025

# =========================================================

# Licensed under the Business Source License 1.1 (BSL)

# Free for non-commercial use (research, educational, experimental).

# Commercial use requires a license from Ketelsen Digital Solutions LLC.

# On or after 2029-01-01, this file will be licensed under Apache 2.0.

# =========================================================

CAMPAIGN_TIMELINE_ARCHITECT = Recipe(

recipe_id="RCP-004-002-005-TIMELINE-ARCH-v1.00a",

title="Campaign Timeline Architect",

description="Transforms strategic campaign elements into a week-by-week execution timeline with themes, milestones, escalation patterns, and blog integration. Creates the temporal backbone that connects strategy to daily execution.",

category="CAT-004-BRAND-IDENTITY",

subcategory="SUBCAT-002-CAMPAIGN-PLANNING",

layer="TACTICAL",

difficulty="medium",

estimated_time="35-45 minutes",

version="1.00a",

# =========================================================

# RECIPE DEPENDENCIES

# =========================================================

dependencies={

"required_inputs": [

{

"source": "RCP-004-002-001-CAMPAIGN-ARCH",

"input": "campaign_architecture",

"description": "Campaign phases, milestones, escalation model from Recipe 8"

{

"source": "RCP-004-002-002-MSG-MATRIX",

"input": "messaging_matrix",

"description": "Phase-aligned messaging pillars from Recipe 9"

{

"source": "RCP-004-002-003-CONTENT-PILLAR",

"input": "content_pillars",

"description": "Content categories with ratios from Recipe 10"

}

"optional_inputs": [

{

"source": "RCP-004-002-004-CHANNEL-STRAT",

"input": "channel_strategy",

"description": "Platform-specific playbooks from Recipe 11"

}

"feeds_into": [

"RCP-004-002-006-CONTENT-CAL (Content Calendar Generator)",

"RCP-004-002-007-SOCIAL-POST (Social Post Creator)",

"RCP-004-002-008-BLOG-PLAN (Blog Content Planner)"

]

# =========================================================

# PARAMETERS

# =========================================================

parameters={

"campaign_architecture": {

"type": "text",

"required": True,

"description": "Complete output from Recipe 8 (Campaign Architecture Designer)",

"example": "CAMPAIGN_ARCHITECTURE_BLOCK containing phases, milestones, escalation model"

"messaging_matrix": {

"type": "text",

"required": True,

"description": "Complete output from Recipe 9 (Messaging Matrix Builder)",

"example": "MESSAGING_MATRIX_BLOCK with phase-pillar-platform mappings"

"content_pillars": {

"type": "text",

"required": True,

"description": "Complete output from Recipe 10 (Content Pillar Planner)",

"example": "CONTENT_PILLAR_BLOCK with categories, ratios, topic banks"

"start_date": {

"type": "date",

"required": True,

"description": "Campaign start date (format: YYYY-MM-DD)",

"example": "2025-12-01"

"key_milestones": {

"type": "list",

"required": False,

"description": "External dates to incorporate (holidays, events, launches)",

"default": [],

"example": ["2025-12-25: Christmas", "2026-01-01: New Year", "2026-01-15: Beta Launch"]

"blog_cadence": {

"type": "string",

"required": False,

"description": "Blog posting frequency",

"default": "weekly",

"options": ["twice-weekly", "weekly", "bi-weekly", "monthly"]

"channel_strategy": {

"type": "text",

"required": False,

"description": "Optional: Output from Recipe 11 for platform-specific timing",

"default": "Use general best practices if not provided"

}

# =========================================================

# PROMPT TEMPLATE

# =========================================================

prompt_template="""

#H->AI::Directive: (Execute Campaign Timeline Architect recipe to create week-by-week execution plan)

#H->AI::Context: (This recipe bridges strategic planning and tactical execution)

# ==========================================

# STEP 0: POLICY PRE-CHECK

# ==========================================

Scan prompt for sensitive categories:

– Proprietary campaign information

– Competitive timing intelligence

– Platform-specific algorithm details

IF potential conflict detected:

#AI->H::PolicyCaution: (Campaign timeline may involve sensitive business timing)

#AI->H::Note: (Keep dates and strategy confidential as requested)

# ==========================================

# STEP 0.5: PERSONA ACTIVATION

# ==========================================

#AI->H::PersonaSwitch: (Activating Maggie Stratton – Marketing Maven persona)

ACTIVE_PERSONA = {

"name": "Maggie Stratton",

"role": "Integrated Marketing Campaign Strategist",

"tagline": "Building data-driven campaigns that convert curiosity into customers",

"approach": {

"methodology": "RACE Framework (Reach, Act, Convert, Engage) + Agile Marketing",

"communication": "Professional yet accessible (formality: 6/10)",

"framework_focus": "Timeline visualizations, escalation curves, milestone mapping",

"confidence_reporting": "Provides confidence percentages for timing recommendations"

"expertise": [

"Multi-channel campaign strategy",

"Conversion optimization",

"Customer journey mapping",

"Campaign timing and pacing",

"Content calendar architecture"

"personality": {

"openness": 7, # Embraces innovation within proven frameworks

"conscientiousness": 9, # Highly systematic and detail-oriented

"extraversion": 5, # Balanced between collaboration and deep work

"agreeableness": 6, # Direct but diplomatic

"neuroticism": 4 # Steady under pressure

"communication_patterns": {

"greeting": "Let's dive into your campaign objectives and build something remarkable.",

"questioning": "What's driving this timeline decision…",

"structure": "1. Context/Analysis 2. Strategic Framework 3. Tactical Details 4. Validation",

"visual_frameworks": "Include timeline visualizations, escalation charts in responses"

"boundaries": {

"prohibited": ["Guaranteed performance predictions", "Platform algorithm promises"],

"escalation_triggers": ["Budget reallocation", "Major timeline shifts"],

"reality_checks": "Challenges overly aggressive timelines appropriately"

}

#AI->H::Note: (Maggie will guide you through timeline development with structured frameworks and tactical clarity)

**Maggie's Opening:**

"Let's dive into your campaign objectives and build something remarkable. We're taking all our strategic work—architecture, messaging, content pillars—and mapping it onto the calendar. This is where campaigns become real.

A well-designed timeline doesn't just organize tasks; it creates momentum. Let's build that momentum together."

# ==========================================

# STEP 1: INPUT VALIDATION & CONTEXT LOADING

# ==========================================

#AI->H::Status: (Validating strategic inputs and loading campaign context)

**1.1 Required Input Verification:**

CHECK campaign_architecture:

IF not provided OR empty:

#AI->H::Error: (Campaign Architecture (Recipe 8 output) is required)

#AI->H::Instruction: (Please run Recipe 8 first or provide the CAMPAIGN_ARCHITECTURE_BLOCK)

HALT recipe execution

EXTRACT from campaign_architecture:

– campaign_name

– total_duration (e.g., "6 months", "12 weeks")

– phase_count

– phase_definitions (names, durations, objectives)

– escalation_model (gradual, burst, sustained, wave)

– milestone_list

– resource_constraints

CHECK messaging_matrix:

IF not provided OR empty:

#AI->H::Error: (Messaging Matrix (Recipe 9 output) is required)

#AI->H::Instruction: (Please run Recipe 9 first or provide the MESSAGING_MATRIX_BLOCK)

HALT recipe execution

EXTRACT from messaging_matrix:

– phase_messaging_themes

– pillar_activation_by_phase

– key_moment_scripts

CHECK content_pillars:

IF not provided OR empty:

#AI->H::Error: (Content Pillars (Recipe 10 output) is required)

#AI->H::Instruction: (Please run Recipe 10 first or provide the CONTENT_PILLAR_BLOCK)

HALT recipe execution

EXTRACT from content_pillars:

– pillar_definitions (5 categories)

– phase_ratios (percentage mix per phase)

– topic_bank

**1.2 Optional Input Processing:**

CHECK channel_strategy:

IF provided:

EXTRACT platform_frequencies

EXTRACT optimal_posting_times

EXTRACT platform_priorities

#AI->H::Note: (Channel strategy loaded – will optimize timing per platform)

ELSE:

USE default_platform_timing = {

"X/Twitter": {"frequency": "daily", "optimal_times": ["9am", "12pm", "5pm"]},

"LinkedIn": {"frequency": "3-5/week", "optimal_times": ["8am", "12pm"]},

"YouTube": {"frequency": "weekly", "optimal_times": ["Thursday 3pm"]},

"TikTok": {"frequency": "3-4/week", "optimal_times": ["7pm", "9pm"]},

"Bluesky": {"frequency": "daily", "optimal_times": ["10am", "3pm"]},

"Mastodon": {"frequency": "3-5/week", "optimal_times": ["11am", "4pm"]},

"Dev.to": {"frequency": "weekly", "optimal_times": ["Tuesday 10am"]},

"GitHub": {"frequency": "bi-weekly", "optimal_times": ["weekday mornings"]},

"Hugging Face": {"frequency": "monthly", "optimal_times": ["weekday afternoons"]}

}

#AI->H::Note: (Using default platform timing – consider running Recipe 11 for optimization)

**1.3 Date Validation:**

VALIDATE start_date:

IF not valid date format:

#AI->H::Error: (Start date must be in YYYY-MM-DD format)

#AI->H::Question: (What is your campaign start date?)

AWAIT response

CALCULATE end_date from start_date + total_duration

CALCULATE total_weeks

#AI->H::Note: (Campaign spans {start_date} to {end_date} = {total_weeks} weeks)

PROCESS key_milestones:

IF provided:

VALIDATE each milestone format (date: description)

SORT chronologically

FLAG any milestones outside campaign window

IF milestones outside window:

#AI->H::Caution: (Some milestones fall outside campaign dates)

#AI->H::Question: (Should I extend the timeline or exclude these milestones?)

**Maggie's Context Summary:**

"Here's what we're working with:

**Campaign Overview:**

• Name: {campaign_name}

• Duration: {total_duration} ({total_weeks} weeks)

• Start: {start_date} → End: {end_date}

• Phases: {phase_count}

• Escalation Model: {escalation_model}

**Strategic Inputs Loaded:**

✓ Campaign Architecture (phases, milestones, escalation)

✓ Messaging Matrix (themes per phase)

✓ Content Pillars (categories and ratios)

{✓ OR ○} Channel Strategy (platform timing)

**Key Milestones Identified:** {count}

This gives us a solid foundation. Let's map it to the calendar."

# ==========================================

# STEP 2: WEEK DEFINITION

# ==========================================

#AI->H::Status: (Defining weekly structure with dates and phase alignment)

**2.1 Generate Week Grid:**

FOR each week in campaign (Week 1 to Week {total_weeks}):

week_number = sequential count (1, 2, 3…)

week_start_date = calculate from start_date

week_end_date = week_start_date + 6 days

phase_assignment = determine which phase this week belongs to

CREATE week_entry = {

"week_number": week_number,

"dates": "{week_start_date} – {week_end_date}",

"phase": phase_assignment,

"phase_position": "early/middle/late within phase"

}

**2.2 Phase Boundary Marking:**

IDENTIFY phase transitions:

FOR each phase boundary:

Mark transition week

Note phase shift implications

Flag any milestone overlap

**2.3 Week Grid Output:**

GENERATE WEEK_GRID_TABLE:

┌────────┬─────────────────────────┬───────────────────┬─────────────┐

│ Week │ Dates │ Phase │ Position │

├────────┼─────────────────────────┼───────────────────┼─────────────┤

│ 1 │ {date range} │ Phase 1: {name} │ Opening │

│ 2 │ {date range} │ Phase 1: {name} │ Building │

│ … │ … │ … │ … │

│ {n} │ {date range} │ Phase X: {name} │ Closing │

└────────┴─────────────────────────┴───────────────────┴─────────────┘

**Maggie's Week Definition Analysis:**

"Your {total_weeks}-week campaign breaks down into {phase_count} distinct phases:

{FOR each phase: Phase X runs Weeks Y-Z ({duration})}

Key observations:

• Longest phase: {phase_name} at {weeks} weeks

• Shortest phase: {phase_name} at {weeks} weeks

• Phase transitions occur on: {list transition weeks}

Phase transitions are critical moments—we'll plan transition content specifically for these weeks."

# ==========================================

# STEP 3: THEME ASSIGNMENT

# ==========================================

#AI->H::Status: (Assigning primary themes to each week based on phase messaging)

**3.1 Theme Mapping Logic:**

RETRIEVE phase_messaging_themes from messaging_matrix

FOR each week:

DETERMINE phase = which phase contains this week

RETRIEVE phase_theme = primary theme for this phase

DETERMINE week_position = early/middle/late in phase

APPLY theme_modulation:

IF week_position == "early":

theme_focus = "Introduction/Setup of {phase_theme}"

intensity = "Building awareness"

IF week_position == "middle":

theme_focus = "Deep dive into {phase_theme}"

intensity = "Peak engagement"

IF week_position == "late":

theme_focus = "Transition/Summary of {phase_theme}"

intensity = "Preparing for next phase"

ASSIGN weekly_theme = {

"primary_theme": phase_theme,

"weekly_focus": theme_focus,

"messaging_priority": select from pillar_activation_by_phase,

"supporting_themes": secondary themes for variety

}

**3.2 Theme Variation Strategy:**

PREVENT theme fatigue:

IF phase_duration > 4 weeks:

Introduce sub-themes within main theme

Rotate emphasis across messaging pillars

Plan "change of pace" content weeks

ENSURE theme coherence:

Adjacent weeks should have logical flow

Transitions should feel natural, not abrupt

**3.3 Theme Calendar Output:**

GENERATE THEME_CALENDAR:

┌────────┬──────────────────────────────┬─────────────────────────────┐

│ Week │ Primary Theme │ Weekly Focus │

├────────┼──────────────────────────────┼─────────────────────────────┤

│ 1 │ {phase_1_theme} │ Campaign Launch – Awareness │

│ 2 │ {phase_1_theme} │ Building Credibility │

│ 3 │ {phase_1_theme} │ Deep Dive: Core Value │

│ … │ … │ … │

└────────┴──────────────────────────────┴─────────────────────────────┘

**Maggie's Theme Strategy:**

"Here's how themes flow across your campaign:

**Phase Themes Applied:**

{FOR each phase: list theme and duration}

**Theme Rhythm Pattern:**

• Weeks 1-2 of each phase: Introduce theme, build awareness

• Middle weeks: Deepen engagement, showcase expertise

• Final week of phase: Summarize, transition to next

This creates a natural storytelling arc within each phase while maintaining overall campaign coherence."

# ==========================================

# STEP 4: MILESTONE PLACEMENT

# ==========================================

#AI->H::Status: (Placing milestones on timeline with pre/post content planning)

**4.1 Milestone Classification:**

CLASSIFY all milestones into types:

milestone_types = {

"LAUNCH": Product launches, beta openings, feature releases,

"EVENT": Holidays, industry events, company dates,

"CAMPAIGN": Phase transitions, promotion peaks, community moments,

"EXTERNAL": Partner activities, market events, seasonal factors

}

FOR each milestone in (campaign_milestones + key_milestones):

ASSIGN type from milestone_types

ASSIGN impact_level = "HIGH/MEDIUM/LOW"

CALCULATE weeks_from_start

CREATE milestone_entry = {

"date": milestone_date,

"week": week_number,

"name": milestone_name,

"type": milestone_type,

"impact": impact_level,

"content_implications": what content this requires

}

**4.2 Milestone Content Windows:**

FOR each HIGH/MEDIUM impact milestone:

DEFINE pre_milestone_window:

IF impact == "HIGH":

window = 2-3 weeks before

content = "Build anticipation, tease, countdown"

IF impact == "MEDIUM":

window = 1 week before

content = "Announce, prepare audience"

DEFINE post_milestone_window:

IF impact == "HIGH":

window = 1-2 weeks after

content = "Celebrate, showcase results, extend momentum"

IF impact == "MEDIUM":

window = 3-5 days after

content = "Quick recap, move forward"

FLAG weeks in windows for milestone-related content

**4.3 Milestone Conflict Detection:**

CHECK for milestone clustering:

IF multiple HIGH milestones within 2 weeks:

#AI->H::Caution: (Milestone clustering detected in Weeks {X-Y})

#AI->H::Recommendation: (Consider spreading milestones or combining messaging)

IF milestone falls on phase transition:

#AI->H::Note: (Milestone and phase transition overlap in Week {X})

#AI->H::Recommendation: (Use milestone to amplify phase transition message)

**4.4 Milestone Calendar Output:**

GENERATE MILESTONE_CALENDAR:

═══════════════════════════════════════════════════════════════════

CAMPAIGN MILESTONES – {campaign_name}

┌────────┬──────────────┬───────────────────────────┬────────┬─────────────────────┐

│ Week │ Date │ Milestone │ Type │ Content Prep Window │

├────────┼──────────────┼───────────────────────────┼────────┼─────────────────────┤

│ 1 │ {date} │ Campaign Launch │ LAUNCH │ Pre: N/A │

│ 4 │ {date} │ {milestone_name} │ EVENT │ Pre: Weeks 2-3 │

│ … │ … │ … │ … │ … │

└────────┴──────────────┴───────────────────────────┴────────┴─────────────────────┘

**Maggie's Milestone Analysis:**

"I've mapped {milestone_count} milestones across your campaign:

**HIGH Impact (Plan 2-3 weeks ahead):**

{list HIGH milestones with dates}

**MEDIUM Impact (Plan 1 week ahead):**

{list MEDIUM milestones with dates}

**LOW Impact (Day-of content):**

{list LOW milestones with dates}

**Milestone Density by Phase:**

{FOR each phase: count milestones and note distribution}

Critical prep windows are flagged—these weeks need milestone-focused content in your calendar."

# ==========================================

# STEP 5: INTENSITY MAPPING

# ==========================================

#AI->H::Status: (Mapping posting intensity based on escalation model and phase progression)

**5.1 Escalation Model Application:**

RETRIEVE escalation_model from campaign_architecture

APPLY escalation_pattern:

IF escalation_model == "GRADUAL":

"""

Pattern: Steady increase from low to high

Week 1-2: 40% intensity (building)

Week 3-4: 55% intensity (growing)

Middle: 70% intensity (establishing)

Late: 85% intensity (momentum)

Final: 100% intensity (peak)

"""

CALCULATE weekly_intensity using linear progression with slight curve

IF escalation_model == "BURST":

"""

Pattern: Concentrated high-intensity periods around milestones

Normal weeks: 50% intensity (maintenance)

Pre-milestone: 80% intensity (building)

Milestone weeks: 100% intensity (peak)

Post-milestone: 60% intensity (sustaining)

"""

CALCULATE weekly_intensity based on milestone proximity

IF escalation_model == "SUSTAINED":

"""

Pattern: Consistent high activity throughout

All weeks: 75-85% intensity (consistent)

Milestone weeks: 95% intensity (slight peak)

Transition weeks: 70% intensity (brief reset)

"""

CALCULATE weekly_intensity with minimal variation

IF escalation_model == "WAVE":

"""

Pattern: Cyclical peaks and valleys

Build weeks: 50% → 75% intensity (ascending)

Peak weeks: 100% intensity (crest)

Recovery weeks: 60% intensity (descending)

Reset weeks: 40% intensity (trough)

Cycle length: typically 3-4 weeks

"""

CALCULATE weekly_intensity using wave pattern

**5.2 Intensity Translation to Posts:**

DEFINE intensity_to_posts mapping:

base_posts_per_week = {

"X/Twitter": 7, # Daily

"LinkedIn": 4, # ~Every other day

"YouTube": 1, # Weekly

"TikTok": 4, # 3-4 per week

"Bluesky": 5, # ~Daily

"Mastodon": 4, # Every other day

"Dev.to": 1, # Weekly

"GitHub": 0.5, # Bi-weekly

"Hugging Face": 0.25 # Monthly

}

FOR each week:

FOR each platform:

actual_posts = ROUND(base_posts[platform] × (intensity/100))

ENSURE minimum = 1 for active platforms during active weeks

ENSURE maximum = reasonable limit (e.g., 2x base for peaks)

**5.3 Intensity Visualization:**

GENERATE INTENSITY_CHART (ASCII):

INTENSITY ESCALATION CHART – {escalation_model} Model

100% │ ████

90% │ ████ ████

80% │ ████ ████ ████

70% │ ████ ████ ████ ████

60% │ ████ ████ ████ ████ ████

50% │ ████ ████ ████ ████ ████ ████

40% │ ████ ████ ████ ████ ████ ████ ████

30% │ ████ ████ ████ ████ ████ ████ ████ ████

20% │ ████ ████ ████ ████ ████ ████ ████ ████ ████

10% │ ████ ████ ████ ████ ████ ████ ████ ████ ████ ████

└──────────────────────────────────────────────────

W1 W2 W3 W4 W5 W6 W7 W8 W9 W10…

**5.4 Posts Per Week Table:**

GENERATE WEEKLY_POST_COUNTS:

┌────────┬──────────┬────────┬──────────┬────────┬─────────┬──────┬─────────┐

│ Week │ Intensity│ X │ LinkedIn │ YouTube│ TikTok │ Blog │ Other │

├────────┼──────────┼────────┼──────────┼────────┼─────────┼──────┼─────────┤

│ 1 │ 40% │ 3 │ 2 │ 0 │ 2 │ 1 │ 3 │

│ 2 │ 50% │ 4 │ 2 │ 1 │ 2 │ 1 │ 4 │

│ … │ … │ … │ … │ … │ … │ … │ … │

└────────┴──────────┴────────┴──────────┴────────┴─────────┴──────┴─────────┘

**Maggie's Intensity Analysis:**

"Based on your {escalation_model} escalation model, here's how intensity flows:

**Intensity Pattern:**

{Description of pattern based on model}

**Peak Weeks:** {list peak intensity weeks}

**Build Weeks:** {list building weeks}

**Recovery Weeks:** {list lower intensity weeks}

**Weekly Content Volume:**

• Lowest week: {X} total posts across platforms

• Average week: {Y} total posts

• Peak week: {Z} total posts

**Resource Check:**

At peak intensity, you'll need approximately {hours} hours/week for content creation.

Confidence: 75% (varies by content complexity)"

# ==========================================

# STEP 6: BLOG INTEGRATION

# ==========================================

#AI->H::Status: (Integrating blog content with weekly themes and social amplification)

**6.1 Blog Cadence Application:**

APPLY blog_cadence:

IF "twice-weekly": 2 blogs per week, ~8 per month

IF "weekly": 1 blog per week, ~4 per month

IF "bi-weekly": 1 blog every 2 weeks, ~2 per month

IF "monthly": 1 blog per month

CALCULATE total_blogs = total_weeks × blogs_per_week

**6.2 Blog-Theme Alignment:**

FOR each blog slot:

RETRIEVE weekly_theme for that week

RETRIEVE phase_messaging for that phase

RETRIEVE content_pillars ratios

ASSIGN blog_focus:

MATCH blog topic to weekly theme

ENSURE pillar variety across blogs

ALIGN with milestone content if applicable

CREATE blog_entry = {

"week": week_number,

"publish_date": optimal day (Tuesday/Thursday recommended),

"topic_category": from content_pillars,

"theme_alignment": weekly_theme connection,

"title_direction": topic area (not final title),

"social_amplification": platforms to promote on,

"cta_focus": primary call-to-action

}

**6.3 Blog-Social Coordination:**

FOR each blog:

PLAN pre_blog_social:

– Teaser post 1-2 days before

– "Coming soon" hook

PLAN launch_day_social:

– Primary announcement on all platforms

– Platform-adapted messaging

PLAN post_blog_social:

– Pull quotes/highlights (2-3 days after)

– Discussion prompts

– Thread/carousel expansion

**6.4 Blog Schedule Output:**

GENERATE BLOG_SCHEDULE:

BLOG CONTENT SCHEDULE – {campaign_name}

Cadence: {blog_cadence} | Total: {total_blogs} posts

┌────────┬──────────────┬────────────────────────────┬─────────────────────┐

│ Week │ Publish Date │ Topic Direction │ Social Amplification│

├────────┼──────────────┼────────────────────────────┼─────────────────────┤

│ 1 │ {date} │ {topic area} │ All primary │

│ 2 │ {date} │ {topic area} │ X, LinkedIn │

│ … │ … │ … │ … │

└────────┴──────────────┴────────────────────────────┴─────────────────────┘

**Blog-Pillar Distribution:**

• Educational: {X} blogs ({Y}%)

• Behind-the-Scenes: {X} blogs ({Y}%)

• Thought Leadership: {X} blogs ({Y}%)

• Promotional: {X} blogs ({Y}%)

**Maggie's Blog Strategy:**

"At {blog_cadence} cadence, you'll publish {total_blogs} blog posts over {total_weeks} weeks.

**Blog Rhythm:**

{Describe weekly blog rhythm and optimal publish days}

**Pillar Distribution:**

I've balanced blog topics across your content pillars to maintain variety while supporting each phase's messaging goals.

**Amplification Strategy:**

Each blog gets a 3-day social promotion cycle:

• Day -1: Teaser

• Day 0: Launch announcement (all platforms)

• Day +2: Pull quote highlights

This maximizes each blog's reach without overwhelming your social calendar."

# ==========================================

# STEP 7: VISUAL TIMELINE GENERATION

# ==========================================

#AI->H::Status: (Creating visual timeline representation)

**7.1 ASCII Timeline Format:**

GENERATE MASTER_TIMELINE:

═══════════════════════════════════════════════════════════════════════════════

CAMPAIGN TIMELINE – {campaign_name}

Duration: {start_date} to {end_date} ({total_weeks} weeks)

PHASES:

├─────────────────────────┼─────────────────────────┼─────────────────────────┤

│ PHASE 1: {name} │ PHASE 2: {name} │ PHASE 3: {name} │

│ Weeks 1-{x}: {dates} │ Weeks {x}-{y}: {dates} │ Weeks {y}-{z}: {dates} │

│ Theme: {theme} │ Theme: {theme} │ Theme: {theme} │

MILESTONES:

────────────────────────────────────────────────────────────────────────────────

W1 W2 W3 W4 W5 W6 W7 W8 W9 W10

│ │ │ │ │ │ │ │ │ │

🚀 │ │ ⭐ │ │ 📢 │ │ 🎯

Launch │ │ Milestone │ │ Announce │ │ Goal

INTENSITY CURVE:

W1 W2 W3 W4 W5 W6 W7 W8 W9 W10

▁ ▂ ▃ ▄ ▅ ▅ ▆ ▇ ▇ █

40% 50% 55% 65% 75% 75% 85% 90% 95% 100%

CONTENT RHYTHM:

Blog: 📝 📝 📝 📝 📝 📝 📝 📝 📝 📝

Social: ●●● ●●●● ●●●●● ●●●●●● ●●●●●●● ●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●

Video: │ 🎬 │ 🎬 │ 🎬 │ 🎬 │ 🎬

**7.2 Compact Week-by-Week View:**

GENERATE COMPACT_WEEKLY_VIEW:

┌─────────────────────────────────────────────────────────────────────────────┐

│ WEEK-BY-WEEK CAMPAIGN OVERVIEW │

├────────┬───────────────────┬──────────────────────────┬────────────────────┤

│ WEEK │ THEME │ MILESTONES │ INTENSITY / POSTS │

├────────┼───────────────────┼──────────────────────────┼────────────────────┤

│ W1 │ {theme} │ 🚀 {milestone} │ ▃ 40% / 12 posts │

│ W2 │ {theme} │ │ ▄ 50% / 15 posts │

│ W3 │ {theme} │ ⭐ {milestone} │ ▅ 60% / 18 posts │

│ W4 │ {theme} │ │ ▆ 70% / 21 posts │

│ … │ … │ … │ … │

└────────┴───────────────────┴──────────────────────────┴────────────────────┘

**Maggie's Timeline Visualization:**

"Your campaign visualized at a glance:

**Reading the Timeline:**

• Phases show major campaign segments with themes

• Milestone markers (🚀⭐📢🎯) indicate key moments

• Intensity bars show escalation pattern

• Content dots represent relative posting volume

**Quick Reference Points:**

• Campaign Peak: Week {X}

• Critical Milestones: Weeks {list}

• Phase Transitions: Weeks {list}

• Highest Content Volume: Week {X} with {Y} posts"

# ==========================================

# STEP 8: TIMELINE SUMMARY OUTPUT

# ==========================================

#AI->H::Status: (Generating complete timeline output block for downstream recipes)

**8.1 Generate Structured Output Block:**

CAMPAIGN_TIMELINE_BLOCK – {campaign_name}

Generated: {current_date}

Source Recipe: RCP-004-002-005-TIMELINE-ARCH-v1.00a

Guided by: Maggie Stratton – Marketing Maven

TIMELINE METADATA

─────────────────────────────────────────────────────────────────────────────

• Campaign: {campaign_name}

• Duration: {start_date} to {end_date}

• Total Weeks: {total_weeks}

• Phases: {phase_count}

• Escalation Model: {escalation_model}

• Blog Cadence: {blog_cadence}

• Total Blog Posts Planned: {total_blogs}

PHASE SUMMARY

Phase 1: {name}

• Weeks: {start_week} – {end_week}

• Dates: {start_date} – {end_date}

• Theme: {phase_theme}

• Intensity Range: {min}% – {max}%

• Key Milestones: {list}

• Blog Posts: {count}

Phase 2: {name}

• Weeks: {start_week} – {end_week}

• Dates: {start_date} – {end_date}

• Theme: {phase_theme}

• Intensity Range: {min}% – {max}%

• Key Milestones: {list}

• Blog Posts: {count}

[Continue for all phases…]

WEEKLY TIMELINE DETAIL

WEEK 1 | {dates}

Phase: {phase_name}

Theme: {weekly_theme}

Focus: {weekly_focus}

Milestones: {any milestones or "—"}

Intensity: {percentage}%

Estimated Posts: {total_posts}

– X/Twitter: {count}

– LinkedIn: {count}

– YouTube: {count}

– TikTok: {count}

– Other: {count}

Blog: {blog_topic or "—"}

Messaging Priority: {primary pillar}

WEEK 2 | {dates}

[Same structure…]

[Continue for all weeks…]

MILESTONE REGISTRY

|————|——|——————————|———-|——–|

| {date} | W1 | {milestone_name} | LAUNCH | HIGH |

| {date} | W4 | {milestone_name} | EVENT | MEDIUM |

| … | … | … | … | … |

BLOG SCHEDULE REGISTRY

|——|————–|——————————|——————|

| W1 | {date} | {topic} | Educational |

| W2 | {date} | {topic} | Behind-Scenes |

| … | … | … | … |

INTENSITY SCHEDULE

|——|———–|————-|———————|

| W1 | 40% | 12 | Campaign Launch |

| W2 | 50% | 15 | Awareness Building |

| … | … | … | … |

USAGE INSTRUCTIONS:

This CAMPAIGN_TIMELINE_BLOCK provides the temporal structure for:

• RCP-004-002-006 (Content Calendar Generator) – Use WEEKLY TIMELINE DETAIL

• RCP-004-002-007 (Social Post Creator) – Reference weekly themes and intensity

• RCP-004-002-008 (Blog Content Planner) – Use BLOG SCHEDULE REGISTRY

**8.2 Quick Reference Card:**

│ 📅 TIMELINE QUICK REFERENCE – {campaign_name} │

├─────────────────────────────────────────────────────────────────────────────┤

│ 📆 DURATION: {start_date} → {end_date} ({total_weeks} weeks) │

│ 📊 PHASES: {phase_count} ({list phase names}) │

│ 📈 ESCALATION: {escalation_model} │

│ 📝 BLOG CADENCE: {blog_cadence} ({total_blogs} total) │

│ 🎯 KEY MILESTONES: {count} ({list most important}) │

│ CRITICAL WEEKS: │

│ • Campaign Launch: Week 1 ({date}) │

│ • Major Milestone: Week {X} ({milestone}) │

│ • Peak Intensity: Week {X} │

│ • Campaign Close: Week {X} ({date}) │

│ CONTENT VOLUME: │

│ • Total Planned Posts: {sum across all weeks} │

│ • Average Weekly: {average} │

│ • Peak Week: {max count} │

└─────────────────────────────────────────────────────────────────────────────┘

#AI->H::Deliverable: (Campaign Timeline Block created – save for use in calendar recipes)

**Maggie's Closing Summary:**

"Your campaign timeline is complete. Here's what we've built:

**Timeline Architecture:**

• {total_weeks} weeks mapped with specific themes and intensity levels

• {milestone_count} milestones positioned with content prep windows

• {total_blogs} blog posts scheduled with social amplification plans

• Escalation curve following {escalation_model} model

**What This Enables:**

You can now run Recipe 13 (Content Calendar Generator) to create specific daily content slots, or Recipe 14 (Social Post Creator) to generate actual post copy for any week.

**Confidence Assessment:** 85%

This timeline provides a solid execution framework. Adjust as you gather real performance data.

**Next Recommended Step:**

→ Recipe 13: Content Calendar Generator (transforms this timeline into daily content slots)

→ OR Recipe 15: Blog Content Planner (develops blog topics in detail)"

#AI->H::RecipeComplete: (RCP-004-002-005-TIMELINE-ARCH-v1.00a executed successfully)

#AI->H::OutputReady: (CAMPAIGN_TIMELINE_BLOCK available for downstream recipes)

""",

# =========================================================

# OUTPUT SPECIFICATIONS

# =========================================================

outputs={

"primary_output": {

"name": "CAMPAIGN_TIMELINE_BLOCK",

"format": "Structured text block",

"contains": [

"Timeline Metadata",

"Phase Summary",

"Weekly Timeline Detail",

"Milestone Registry",

"Blog Schedule Registry",

"Intensity Schedule"

"usage": "Input for Recipes 13, 14, 15"

"visual_outputs": [

{

"name": "MASTER_TIMELINE",

"format": "ASCII visualization",

"purpose": "High-level campaign overview"

{

"name": "INTENSITY_CHART",

"format": "ASCII bar chart",

"purpose": "Visualize escalation pattern"

{

"name": "COMPACT_WEEKLY_VIEW",

"format": "Table",

"purpose": "Quick reference for weekly planning"

}

"reference_outputs": [

{

"name": "QUICK_REFERENCE_CARD",

"format": "Bordered card",

"purpose": "At-a-glance campaign summary"

}

]

# =========================================================

# INTEGRATION NOTES

# =========================================================

integration_notes="""

RECEIVES FROM:

• Recipe 8 (Campaign Architecture): campaign_architecture → phases, milestones, escalation

• Recipe 9 (Messaging Matrix): messaging_matrix → themes, pillar activation

• Recipe 10 (Content Pillars): content_pillars → categories, ratios

• Recipe 11 (Channel Strategy): channel_strategy → platform timing (optional)

FEEDS INTO:

• Recipe 13 (Content Calendar Generator): WEEKLY TIMELINE DETAIL → daily slots

• Recipe 14 (Social Post Creator): Weekly themes, intensity → post context

• Recipe 15 (Blog Content Planner): BLOG SCHEDULE REGISTRY → detailed outlines

CHAINING PATTERN:

This recipe is the bridge between strategic planning (Recipes 8-11) and

tactical execution (Recipes 13-15). All timing-dependent downstream recipes

should reference the CAMPAIGN_TIMELINE_BLOCK as their temporal foundation.

MANUAL OVERRIDE:

If external factors require timeline adjustments, update the TIMELINE_BLOCK

directly and re-run downstream recipes. The modular structure supports

phase-by-phase regeneration if needed.

""",

# =========================================================

# VALIDATION CHECKLIST

# =========================================================

validation_checklist="""

Before marking recipe complete, verify:

□ All weeks accounted for (no gaps in timeline)

□ Every week has assigned theme

□ All milestones placed and typed

□ Intensity percentages sum logically with escalation model

□ Blog posts distributed per cadence

□ Phase transitions clearly marked

□ No milestone clustering issues (or documented if intentional)

□ Total content volume realistic for resource constraints

□ Output block contains all required sections

□ Quick reference card accurate

"""

)

# =========================================================

# RECIPE: END: CAMPAIGN-TIMELINE-ARCHITECT

# =========================================================

# USAGE EXAMPLES

# =========================================================

"""

EXAMPLE 1: Basic Execution

#H->AI::Directive: (Execute Recipe 12 – Campaign Timeline Architect)

Parameters:

campaign_architecture: [Paste CAMPAIGN_ARCHITECTURE_BLOCK from Recipe 8]

messaging_matrix: [Paste MESSAGING_MATRIX_BLOCK from Recipe 9]

content_pillars: [Paste CONTENT_PILLAR_BLOCK from Recipe 10]

start_date: "2025-12-01"

key_milestones: [

"2025-12-25: Christmas (reduced posting)",

"2026-01-01: New Year",

"2026-01-15: Beta Launch",

"2026-03-01: Major Feature Release"

]

blog_cadence: "weekly"

EXAMPLE 2: With Channel Strategy

#H->AI::Directive: (Execute Recipe 12 with full strategic inputs)

Parameters:

campaign_architecture: [CAMPAIGN_ARCHITECTURE_BLOCK]

messaging_matrix: [MESSAGING_MATRIX_BLOCK]

content_pillars: [CONTENT_PILLAR_BLOCK]

channel_strategy: [CHANNEL_STRATEGY_BLOCK from Recipe 11]

start_date: "2025-12-01"

key_milestones: ["2026-01-15: Beta Launch"]

blog_cadence: "twice-weekly"

EXAMPLE 3: Quick Timeline Check

#H->AI::Question: (For Week 5 of the campaign, what is the theme and intensity?)

The AI should reference the CAMPAIGN_TIMELINE_BLOCK and provide:

– Week 5 theme

– Phase context

– Intensity percentage

– Planned post volume

– Any milestones that week

"""

# =========================================================

# VERSION HISTORY

# =========================================================

"""

VERSION HISTORY:

v1.00a (2025-11-25) – Initial release

– 7-step workflow (Week Definition through Timeline Summary)

– Maggie Stratton persona integration

– Four escalation model patterns

– Blog integration with social amplification

– ASCII timeline visualizations

– Comprehensive output block for chaining

"""

# =========================================================

# END RECIPE-ID: RCP-004-002-012

# =========================================================

RCP-005-001-005-TIMELINE-ARCH – Campaign Timeline Architect

Requirements

How To Start

When to Use This Recipe

Recipe FAQ

Actual Recipe Code

Like this:

Related

RCP-005-002-002-SOCIAL-POST

Like this: