Compound Writing: How I Turned My Process Into a Plugin
Why this is in the vault
Direct instance of the same skills/plugins pattern RDCO already runs (this very note was filed by a skill, /process-newsletter) — Parrott names the mechanism explicitly and ships it as an installable artifact, which is worth studying as a packaging model.
The core argument
Katie Parrott (Every staff writer, "Working Overtime" column) argues the "did AI or a human write this" framing is the wrong question — writing is a multi-stage process (interviewing, outlining, drafting, editing) and AI can assist well or badly at each stage. She narrates building "Compound Writing," a personal writing methodology developed over six months, modeled explicitly on Every colleague Kieran Klaassen's "Compound Engineering" ([[2026-01-30-every-compound-engineering-framework]]) and co-founder Dan Shipper's "agent-native architectures" framing.
The mechanics evolve in four stages: (1) early freeform chat threads where insights got buried and lost between sessions; (2) Anthropic Projects (persistent style guides — voice documentation plus sample essays available across chats); (3) Anthropic Skills (discrete, invokable methods for a specific job — an "interview skill" that draws out her thinking without supplying the argument, an "editing skill" that checks structure before sentence-level polish); (4) Claude Code plugins, which bundle multiple skills so someone else can install the whole package — the plugin is the distribution mechanism.
The load-bearing mechanic isn't the tooling ladder, it's the feedback loop: after each piece, lessons get written back into the system — "a recurring aversion can become a guardrail; a sentence-level preference can become an instruction the agent reads on the next piece." The system gets more specific to her the more she uses it. She calls it "a writing gym" — the skills are equipment, she decides what to push. Deliverables: a public guide (every.to/guides/compound-writing) and an open-source plugin on GitHub (github.com/EveryInc/compound-writing). This piece launches Every's new "How We Write Now" series (Laura Entis and Mike Taylor pieces to follow, closing with a live write-along).
Mapping against Ray Data Co
This is the same shape as /skillify ([[2026-04-22-garry-tan-skillify-it-workflow]]; ~/.claude/skills/skillify/) — RDCO's own "turn a workflow that just worked into a permanent skill" pattern — and as the implementation-notes-sub-agent pattern ([[2026-05-18-implementation-notes-pattern-for-sub-agent-dispatches]]): both are instances of writing this-session's lesson back into a durable instruction artifact so the next run starts smarter. Parrott's four-stage ladder (freeform chat → Projects/style-guide → Skills → Plugin-as-distribution) is a clean vocabulary for something RDCO does informally but hasn't named: the newsletter-processing skill itself has been iterated exactly this way — reference/vault-note-schema.md exists because schema drift got caught and pinned down, and the README's per-sender gotcha sections (SDG sponsor patterns, Not Boring co-author bias, this file's own Every sponsor-observation log) are literally Parrott's "recurring aversion becomes a guardrail" mechanic applied to newsletter triage instead of prose. Worth an explicit gap-check: does RDCO have anything that plays the "compounding" role for voice specifically (a living style-guide skill for Sanity Check drafts, not just process skills)? draft-review checks against existing voice but doesn't visibly write new voice rules back after each issue — that write-back step is the piece Parrott's plugin makes concrete and RDCO's writing skills don't yet do.
⚠️ Sponsorship
No paid third-party sponsor block in this issue (checked plaintext and HTML; the only .advertisement CSS hit is unused template boilerplate). Standard Every house footer cross-promo present: "Every All Access" bundle CTA, and the sister-publication block — Sparkle ("Organize your Mac with AI"), Cora ("The most human way to do email"), Spiral ("Repurpose your content endlessly"), Monologue ("Effortless voice dictation for your Mac") — plus a UTM-tagged internal paywall CTA pointing to Every's own products page. All self-promo, no undisclosed third-party relationship. Consistent with the 2026-08-24 observation in the whitelist README that Brief (briefhq.ai) remains a one-off sponsor rather than a recurring relationship.
Related
- [[2026-01-30-every-compound-engineering-framework]]
- [[2026-02-09-every-compound-engineering-guide]]
- [[2026-03-30-ae-roundup-agent-skills-expertise]]
- [[feedback_implementation_notes_sub_agent_pattern]]