The Content Pipeline Example
This is a member-only chapter. Log in with your Signal Over Noise membership email to continue.
Log in to readModule 3 · Section 4 of 6
The Content Pipeline Example
This one gets explained in detail because it illustrates the full build-once pattern.
The problem: I was spending too much time moving content from raw idea to publishable draft. The steps were consistent — research, structure, draft, review — but I was doing them manually each time, which meant context-switching between tools and forgetting which stage I was at.
The solution: a skill that handles each stage in sequence, with a subagent for each step.
The pipeline works like this:
- Raw note lands in
content/inbox/— could be a title and a few bullet points, or a full rough draft - The pipeline detects the file and reads it
- Stage 1: a research subagent looks up any claims that need verification and appends a sources section
- Stage 2: a structure subagent assesses whether the piece has a clear point and logical flow, and adds an outline if it doesn’t
- Stage 3: a draft subagent expands the piece to target length, following voice guidelines from VOICE.md
- Stage 4: the draft-reviewer skill runs and flags any issues
- Output goes into
content/review/with a summary of what was changed and what the reviewer flagged
I review what’s in content/review/ and either approve it as-is, make edits, or send it back through with additional instructions.
The build time was roughly two hours. The skill has processed dozens of pieces since. The consistent quality floor it enforces — same voice, same reading level, same review criteria every time — is something I couldn’t maintain manually without a lot of effort.