How I Built a Blog Post Pipeline with Parallel Critics
The sequential editor waits for each pass to finish. The parallel critics do not wait for each other.
sequential editing: parallel critics:
────────────────── ─────────────────
draft draft
↓ ↓
structure check ┌───┴───┐───────────┐
↓ │ │ │
style check slop rhythm facts
↓ │ │ │
fact check clichés pacing proof
↓ └───┬───┘───────────┘
final polish ↓
one edit passFour eyes on the same text at once. None of them know what the others found.
The skill that writes does not know what to ask. So it must ask before it writes.
without questions: with questions:
────────────────── ───────────────
2000 words 500 words
generic phrases concrete details
"AI is a powerful tool" the actual thing builtThe blank page answers you back. You answer the wrong question. Both of you have wasted time.
what the critics caught in this draft:
7 hedging words ── "maybe", "something like"
3 monotonous lists ─ identical bullet lengths
5 vague claims ── no examples given
2 wrong facts ── needed checkingA human passes through the same text four times and misses what the second pass already accepted.
The agent does not read what it has already approved. It only reads what it was asked to find.
One skill lives in one place. Symlinks carry it everywhere.
~/.claude/skills/blogpost-pipeline/
↓
project-A/ → symlink
project-B/ → symlink
project-C/ → symlinkThe knowledge does not duplicate. The path to it is short from anywhere.
The old skill and the new skill had the same name. The confusion was not in the names. The confusion was in keeping both.
Delete the old. Walk forward without looking back.
— Ilao Dzindin