Content Marathon — 14-Day Orchestrator

run

Called by the scheduled trigger (or manually). This is the core execution loop.

1. Read content-calendar.json
2. Determine current slot: morning (before 1pm local) or evening (after 1pm)
3. Find the next unposted item for today + current slot
4. If no items for today: check for overdue items from previous days, process the oldest one
5. If item found:
   • For R (ready) items: read source, verify numbers, format for platform, commit
   • For E (edit) items: spawn an Agent to read research source and draft the post, commit
   • For W (write) items: spawn an Agent to write from resume + repo code, commit
6. Update item status to "drafted" in content-calendar.json
7. Commit calendar state
8. Display the formatted content for manual posting
9. If all 28 items are "drafted" or "posted": send completion notification, cancel triggers

status

Delegate to /content-queue status. Show: posted/drafted/ready/overdue counts, today's items, days remaining.

stop

1. List active triggers via /schedule list
2. Cancel the morning and evening content-marathon triggers
3. Report: items completed, items remaining, final stats

catchup

Process all overdue items (date < today, status = ready) in chronological order. Useful after vacation or missed days.

1. Find all overdue items
2. Process each one via the run logic
3. Report how many were caught up

Calendar Template

Initialize with this exact schedule (Apr 17-30, 2026):

Day 1  Apr 17  AM: #1  Dev.to mcpkit launch (R/30m)
Day 1  Apr 17  PM: #3  Twitter thread (R/20m)
Day 2  Apr 18  AM: #2  Show HN mcpkit v2 (R/45m)
Day 2  Apr 18  PM: #4  r/golang post (R/15m)
Day 3  Apr 19  AM: #6  MCP Registry submission (R/60m)
Day 3  Apr 19  PM: #5  awesome-go PR (R/30m)
Day 4  Apr 20  AM: #8  MCP Tool Design Patterns (E/120m)
Day 4  Apr 20  PM: #54 Gist promotion thread (R/25m)
Day 5  Apr 21  AM: #9  Go MCP Ecosystem Gap (E/90m)
Day 5  Apr 21  PM: #10 MCP Quickstart Tutorial (E/90m)
Day 6  Apr 22  AM: #12 Deferred Tool Loading (E/75m)
Day 6  Apr 22  PM: #13 Multi-Protocol Gateway (E/90m)
Day 7  Apr 23  AM: #14 OpenAPI-MCP Bridge (E/60m)
Day 7  Apr 23  PM: #16 MCP Security (E/90m)
Day 8  Apr 24  AM: #17 23 Agents BFT (W/120m)
Day 8  Apr 24  PM: #18 Durable Execution (W/100m)
Day 9  Apr 25  AM: #19 Token Budgeting 90% (W/100m)
Day 9  Apr 25  PM: #20 503 R&D Tasks (E/75m)
Day 10 Apr 26  AM: #21 Cascade Routing 70% (E/75m)
Day 10 Apr 26  PM: #25 JSON Failures Compound (E/90m)
Day 11 Apr 27  AM: #29 6,200-Job Queue P0 (W/90m)
Day 11 Apr 27  PM: #28 Zero-Downtime Migration (W/75m)
Day 12 Apr 28  AM: #44 OWASP Agentic Top 10 (E/100m)
Day 12 Apr 28  PM: #45 MCP Security Playbook (E/90m)
Day 13 Apr 29  AM: #33 CI/CD 76-Repo Patterns (E/90m)
Day 13 Apr 29  PM: #34 Git Secret Removal (E/75m)
Day 14 Apr 30  AM: #60 397 Rules, 76 Repos (E/75m)
Day 14 Apr 30  PM: #50 Conference Talks (R/45m)

Interview-day guidance

• Apr 17 (Retool): Both items are R (ready) — no writing needed
• Apr 21 (Crusoe): Cap content work at 90 min, defer PM to evening
• Apr 23 (Google Cloud): AM item is short edit (60m), PM item is post-interview

Notes

• The marathon is content DRAFTING, not posting. Human reviews and posts manually.
• For GitHub PRs (awesome-go, awesome-list): the content_writer can create PRs directly.
• All content goes through security verification before commit.
• If a day is skipped entirely, catchup mode processes overdue items.