GitHub: EveryInc compound-writing plugin
GitHub
GitHub’s EveryInc released Compound Writing, a plugin that guides writers from notes to publishable drafts. It tries to help without boxing people into one workflow, and it works in Claude and Codex.
Based on reporting by GitHub — read the original for the full story.
Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error
EveryInc’s Compound Writing is trying to solve a very specific problem: how to give writers a full toolbox without forcing them to learn a ritual before they can get anything done. The plugin bundles a context-first system for developing ideas, drafting, revising, stress-testing, and getting work ready for publication. It ships from one canonical source tree and is packaged for both Claude and Codex.
The front door is cw-scribe, which is meant for open-ended work. A writer can paste in notes, start from a draft, or just describe the job in ordinary language. On a first meaningful interaction, Scribe looks for a draft, an active workspace, and useful writing context. If there isn’t one, it explains why a portable writing home helps, asks where it should live, and creates the basic structure with VOICE.md, STYLE.md, examples/, and drafts/.
That structure is doing a lot of the actual philosophy work. VOICE.md is for syntax, diction, and tone. STYLE.md handles argument, evidence, structure, standards, and publication readiness. AUDIENCE.md is optional, and it can be shared across publications when needed. The plugin also says it will preserve existing workspaces instead of retrofitting them, and it follows repository, global, project, assignment, and voice context in that order of authority.
There’s no giant mandatory pipeline here, either. Compound Writing maps tasks to skills, but it treats that map as guidance, not a gate. cw-brainstorm, cw-outline, cw-draft, cw-dev-edit, cw-line-edit, cw-reader, cw-objections, and cw-final-pass are all there when a user wants them. But if the user just wants help finishing a piece, Scribe is supposed to pick the smallest useful workflow and get out of the way.
My take — AI-written commentary, not fact-checked reporting
This is the right instinct: less wizard costume, more working system. A lot of writing tools confuse “power” with making people memorize ten commands before lunch, and that’s usually just disrespect with documentation. Compound Writing sounds like it knows the difference between helping a writer and auditioning for the role of local deity.
Read more about this at: GitHub
