content-pipeline

Content Pipeline Skill

Aggregator pattern: 이 skill은 content를 수집하지 않음. monitoring — watch, don't prompt.

• Synthesize in batches. One cycle produces blog draft + X thread + LinkedIn.
• Track narrative arc. Posts accumulate into a story. Season/episode structure keeps continuity.
• Start simple. One agent profile + cron job + one tracking file. No multi-stage pipeline unless proven necessary.

Modes

Mode A: Aggregator (external → blog)

Collect from external sources (trend-harvester, SEO-harvester), select topics, assign to content-writer via kanban. Suitable for: trend posts, SEO-optimized evergreen, tool roundups.

Mode B: CMO Agent (internal work → content)

Single autonomous agent profile (content-manager) observes Drew's recent work and produces multi-format content. Runs daily at 12:00 KST via cron.

Trigger: Cron (0 12 * * *), deliver to Discord #content-channel. Profile: ~/.{{AGENT_NAME_LOWER}}/agents/content-manager.md (deepseek-v4-pro, tools: terminal, file, search, session_search, web) Skill prerequisites: content-pipeline (this skill), SVG knowledge, Excalidraw, Mermaid. Suitable for: build logs, troubleshooting deep-dives, architecture decisions, project retrospectives.

See references/cmo-agent-mode.md for the full implementation guide.

Mode B requires these knowledge base files (in P4-cortex/content/):

• brand-guide.md — brand positioning, voice, audience
• glossary.md — project terms ({{AGENT_NAME}}, M-LOG, PDC...)
• content-inventory.md — published/drafted content for dedup
• narrative_arc.md — episode tracking, season structure, continuity

The agent reads all four at the start of every cycle before gathering context.

---

Editorial North Star

YOUR_DOMAIN은 자동 뉴스 블로그가 아니라 Drew가 AI, 도구, 코드, 글쓰기, 시스템 설계를 통해 어떻게 사고하고 만드는지를 보여주는 개인 작업실이다.

공개 후보가 되는 글은 반드시 아래 등식을 만족해야 한다:

public-worthy content = 기록 + 해석 + 재사용 가능한 통찰

단순한 수집 결과, 출시 소식, 활동 보고, 링크 요약은 공개 draft로 만들지 않는다. 그런 항목은 raw 또는 archive에 남겨도 되지만 content board task로 승격하지 않는다.