Master Execution Plan — CampaignForge Specs

~60

Platform Tasks

~25

ContentForge Tasks

~40

Operate Tasks

Gate Milestones

Cross-Dependencies

Why ContentForge Can Run Fully In Parallel

ContentForge (Astro + Svelte to Cloudflare Pages) and CampaignForge (SvelteKit to Coolify) share zero code, zero infrastructure, and zero deployment targets. The only shared dependency is spec approval (Phase 0 gate). After that, they're independent build tracks that a single Claude agent can alternate between -- or two agents can run simultaneously via Conductor worktrees.

The Current Site Is the Safety Net

degreesources.com is live and working. The ContentForge migration runs on a preview branch. Each tool is A/B tested (old HTML vs new Svelte) before switchover. If anything degrades conversion, the old site is one git revert away. Zero downtime, zero risk to revenue during migration.

3-Track Gantt -- Week by Week

Blue = CampaignForge platform. Green = ContentForge content site. Orange = Operate (social, ads, tracking). Red = Gate milestones.

CampaignForge (SvelteKit → Coolify)

ContentForge (Astro + Svelte → CF Pages)

Operate (social, ads, tracking)

Gate (blocks downstream)

	W0	W1	W2	W3	W4	W5	W6	W7	W8	W9	W11	W12	W13	W14	W15+
Phase 0 -- Approval & Foundation This Week
Spec Review (all 5 docs)	REVIEW
Social Profiles (7 platforms)	CREATE	daily posting → ongoing forever
Entity Resolution + DUNS	BLOCKER
GATE 0: Spec approved	G0
Phase 1 -- Foundation Weeks 1-3 • Two independent BUILD tracks launch simultaneously
CampaignForge BUILD Track (SvelteKit → Coolify)
SvelteKit scaffold + schema		scaffold
Auth + app shell + Postgres
Agent executor + pipeline			agent SDK
Brief editor + pipeline UI + deploy				UI + deploy
ContentForge BUILD Track (Astro + Svelte → Cloudflare Pages) NEW
Astro scaffold + Tailwind tokens		scaffold + tokens
Layouts + content migration (MDX)			JSON → MDX
Tool migration: EFC + Quiz + Finder				3 priority tools
Tool migration: remaining 7 tools					parallel	7 tools
SEO: schema + E-E-A-T pages					schema + about
Tracking: Zaraz events + CAPI map						events + CAPI
Lighthouse + E2E + A/B → GO LIVE							GO LIVE
OPERATE Track (Operator Executes)
Tracking setup (Zaraz + CAPI)		pixel + domain
Ad account setup + campaigns			build campaigns PAUSED
Ad warm-up (Meta → Google → Bing)			$5	$15-25	$50+	$100+	$200+	scale → steady state
Gate Milestones
G1: Tracking verified		G1
G1.5: Platform MVP deployed				G1.5
G-CF: ContentForge live on Astro							G-CF
G2: Full workflow in UI							G2
Phase 2+ -- Core Workflow + Scale Weeks 4-6 onwards • ContentForge is live, campaigns land on Astro site
Core workflow UI (strategy → export)						copy + creative	export + lander
First live campaign via platform							generate → upload → test	retro
Phase 3: Intel + Email + Automation									Listmonk + GrowthBook	n8n + health
GrowthBook on ContentForge									A/B tests live	ongoing A/B optimization
Phase 4-5: APIs + Scale											Meta + Google APIs	TikTok + CAPI	retro auto	attribution	ping/post

Phase Detail Cards

Each phase with its dual-track lane view, task breakdown, and gate milestones.

Phase 0: Approval & Brand Foundation

This Week • 22 tasks

Lock the spec. Set up social presence. Unblock account creation.

SPEC + OPERATE Track

0.1Review platform specOperator

0.2Review operator runbookOperator

0.3Review trust frameworkOperator

0.5Resolve Click Send Inc entity (BLOCKER)Operator

0.6Get DUNS numberOperator

0.21Subscribe Meta Verified ($14.99/mo)Operator

SOCIAL Track (no dependencies)

0.7-13Create 7 DegreeSource social profilesOperator

0.14Branded banners/covers for all profilesOperator

0.15Platform-specific bios + UTM linksOperator

0.16-18Pre-warm 3 future vertical profilesOperator

0.19Prepare 10 social posts (tool highlights)Claude+Op

0.20Prepare curated posts for future verticalsClaude+Op

🚧

GATE 0.22: Spec approved + social profiles live + Meta Verified active → unlocks Phase 1

Phase 1: Foundation

Weeks 1-3 • 35 tasks

Tracking live on degreesources.com. Platform MVP deployed. Organic posting daily. Ad accounts created.

BUILD Track -- CampaignForge

1.15SvelteKit scaffold + Tailwind 4 + shadcnClaude

1.16-18Drizzle schema: core + agents + pipelineClaude

1.19Postgres on Coolify + migrationsClaude

1.20Simple session gate authClaude

1.21App shell: sidebar, dark mode, responsiveClaude

1.22-24Agent executor + cost tracker + sessionsClaude

1.25-28Pipeline orchestrator + brief editor + UIClaude

1.29Deploy to Coolify (platform.fourthright.io)Claude

OPERATE Track -- Tracking + Ads + Social

1.1Install Meta Pixel via ZarazClaude

1.2-4Domain verify + ad account + paymentOperator

1.5-9Google Ads setup + verification + conversionsOp+Claude

1.10CAPI relay on Cloudflare WorkerClaude

1.11Verify tracking end-to-endOp+Claude

1.12-13Build campaign structures (PAUSED)Claude

1.31-35Daily social posting + engagementOperator

🚧

GATE 1.14: Tracking verified + ads ready | GATE 1.30: Platform MVP → unlocks Phase 2

Phase 2: Core Workflow + Warm-Up

Weeks 4-6 • 26 tasks

Full campaign workflow UI. Ad accounts warm and spending. First live campaign generating data.

BUILD Track -- Workflow UI

2.12Strategy browser: angle cards + approve/rejectClaude

2.14-16Copy workspace + QA scores + comparisonClaude

2.17-18Creative gallery + R2 integrationClaude

2.19Export center (XLSX, CSVs, ZIP)Claude

2.20Landing page builder + live previewClaude

2.21Campaign overview: status timelineClaude

OPERATE Track -- Ad Warm-Up + First Campaign

2.1Meta: engagement campaigns $5-10/dayOperator

2.2Google Search: $50/day, Max ClicksOperator

2.4Meta: traffic/leads $15-25/day (+20%/day max)Operator

2.5Bing: import from Google, bids -30%Operator

2.7Meta: conversion campaigns $50+/dayOperator

2.23Generate first campaign via platform UIOp+Claude

2.24-26Upload → 7-day test → first retro → VaultOperator

🚧

GATE 2.11: All accounts through learning | GATE 2.22: Full workflow brief→export in UI → unlocks Phase 3

Phase 3: Intelligence + Email + Automation

Weeks 7-9 • 28 tasks

Lead intelligence live. Email capture converting. Social posting automated. Competitive monitoring running.

BUILD Track

3.1-5Lead intelligence (SVAR DataGrid + maps + dashboard)Claude

3.6-8Listmonk deploy + MJML templates + tool captureClaude

3.9-11GrowthBook deploy + first A/B experimentsClaude+Op

3.12-16n8n deploy + social automation workflowsClaude

3.17-21Platform health + competitive intel + fatigue detectClaude

3.22-27Directus collections + 5 Metabase dashboardsClaude

OPERATE Track

--Continue daily social posting cadenceOperator

--Campaign performance monitoring (daily)Operator

--Weekly A/B test review + implement winnersOperator

--Weekly competitive intel review (Monday)Operator

--Campaign retros (Friday, 7+ day campaigns)Operator

🚧

GATE 3.28: Email capturing, social automated, intel monitoring, platform health tracked → unlocks Phase 4

Phase 4-5: Ad Platform APIs + Scale

Weeks 10+ • 15+ tasks

Live ad metrics in platform. Server-side tracking. Campaign retro automated. Multi-vertical expansion.

BUILD Track -- Phase 4

4.1-2Meta Marketing API + Google Ads API integrationClaude

4.3-4Daily metric pull cron + performance dashboardClaude

4.5-8TikTok + Bing APIs + CAPI relay + Zaraz configClaude

4.9-11Campaign retro automation + fatigue alerts + attributionClaude

BUILD Track -- Phase 5

5.1-2Evaluate Inngest + ping/post routing engineClaude

5.3-5Buyer management + revenue tracking + fraud detectionClaude

5.6-7Multi-vertical: auto-insurance research + campaignsOp+Claude

5.8-9Campaign push to platforms + agent-driven contentClaude

🚧

GATE 4.15: Live metrics, CAPI firing, retro automated → unlocks Phase 5 scale operations

Cross-Track Dependencies -- Almost None

The two BUILD tracks are independent. The only touchpoint is Phase 3 when GrowthBook deploys on the platform and integrates into ContentForge.

CampaignForge does NOT depend on ContentForge for:

✓ Platform scaffold, DB schema, auth

✓ Agent executor, pipeline orchestration

✓ Brief editor, strategy browser, copy workspace

✓ Creative gallery, export center

✓ Lead intelligence, analytics, Metabase

✓ Ad platform API integrations

ContentForge does NOT depend on CampaignForge for:

✓ Astro scaffold, Tailwind tokens, layouts

✓ Content migration (JSON to MDX)

✓ Tool migration (vanilla JS to Svelte 5)

✓ SEO (schema markup, E-E-A-T pages, sitemaps)

✓ Zaraz event tracking + CAPI mapping

✓ Deployment to Cloudflare Pages

The One Touchpoint: Phase 3 -- GrowthBook + Email

When GrowthBook deploys on the CampaignForge infrastructure (Week 8), it integrates into ContentForge for A/B testing. Similarly, Listmonk email capture triggers get wired into ContentForge tool pages. Before Phase 3, ContentForge runs independently. After Phase 3, they're connected through GrowthBook experiments and Listmonk opt-ins -- but still separate codebases and deploys.

Ongoing Rhythms -- Start and Never Stop

Recurring operations that begin during early phases and persist forever.

Daily (Starts Phase 0)

DegreeSource social posting1x/day

Message response (<15 min)continuous

Future vertical curated posts2x/week each

Education community engagement5+/week

Daily (Starts Phase 2)

Morning dashboard "Read"daily AM

Platform-specific optimizationdaily rotate

Monthly P&L reviewend of month

Weekly (Starts Phase 3)

Competitive intel reviewMonday

Platform intelligence digestMonday

A/B test review + winnersWednesday

Campaign retros (7+ day)Friday

Infrastructure health checkFriday

Gov data refresh1st of month

Why ContentForge Should Land by Week 6

Three reasons the content site migration should complete before the first real campaign launches.

1. Ads Land on the New Site

The first live campaign (Week 6-7) sends ad traffic to degreesources.com. If ContentForge is live by then, that traffic lands on a 95+ Lighthouse site with proper schema, event tracking, and A/B-ready CTAs -- not the old plain HTML site. Every dollar of ad spend from day one benefits from the improved architecture.

2. Tracking Events Need Astro

The event taxonomy (tool_start, tool_complete, cta_click) feeds Meta CAPI for optimization. Instrumenting these events on the old vanilla JS tools is possible but fragile. Instrumenting them on Svelte components is clean, testable, and maintainable. Build tracking into the new architecture from the start.

3. Meta HiVA Cares About Landing Pages

Meta's landing page quality assessment runs continuously. A faster, better-structured site (0 KB JS on articles, 5 KB on tools, proper OG tags, semantic HTML) directly improves the HiVA score during the critical warm-up window. Starting warm-up on the old site then switching mid-flight risks a score recalculation.