avatar vian's notes

Learning in public, one post at a time

  • HOME
  • CATEGORIES
  • TAGS
  • ARCHIVES
  • ABOUT
Home How I Used AI Agents As My Editorial Pipeline
How I Used AI Agents As My Editorial Pipeline

How I Used AI Agents As My Editorial Pipeline

LinkedIn Post (Text-Only, Teaser)

Two drafts. One tried to squeeze six months of decisions into a single 3,000-word post. The other was a flat walkthrough that never said why anyone should care.

Both had strong material. Both had structural problems.

I ran them through an AI editorial pipeline — not to write for me, but to review, critique, and iterate until the structure held.

Five phases: lead agent review, iterative revision (including catching its own fabricated story), cold-read by fresh agents who didn’t know what they were reading, content mapping into a 9-post series, parallel execution with one agent per post.

The AI didn’t write a word of the final posts. It told me where drafts were missing. I filled the gaps.

The process is replicable. Same pipeline works for any draft — critique, rewrite, cold-read, restructure, execute. I packaged it into a reusable /writer command so I don’t rebuild the process every time. The agents change. The structure stays.

It’s not faster writing. It’s more deliberate writing.

#AIAgents #Writing #DeveloperTools #AIDevelopment #TechnicalWriting


Comment (First Comment)

Full story on Medium → https://alvian.medium.com/how-i-used-ai-agents-as-my-editorial-pipeline


Notes

  • Schedule via Fedica for D+1 (Sep 29) — https://fedica.com/
    • Post text-only (no links in main body)
    • CTA: teaser ends with a hook
    • Comment: “Full story on Medium → https://alvian.medium.com/how-i-used-ai-agents-as-my-editorial-pipeline”
    • Schedule comment to post immediately after post goes live
    • Wait 10-15 minutes before engaging with comments

Recently Updated

  • Headroom, Round Two: Four Walls Between Me and a Working Token Saver
  • The Server Split That Almost Didn't Happen
  • I Opened My First Open Source PRs. None of Them Are Merged Yet.
  • Checking Upstream: What v0.5.50 Gained for 9router
  • The 403 That Wasn't: How Warp, 9router, and Cloudflare Masked Two Separate Failures

Trending Tags

9router technical tooling ade ai personal postmortem warp agents orchestration

© 2026 Alvian. Some rights reserved.

This blog is open source — view on GitHub

Using the Chirpy theme for Jekyll.

Trending Tags

9router technical tooling ade ai personal postmortem warp agents orchestration