A WRITING PIPELINE FOR CODING AGENTS · v0.7

Velith

Books to the human-quality bar.

Six phases take a book from a blank page to a publishable EPUB — and hold every chapter, every edit, and every image to one standard: a cold reader who buys books in this genre cannot tell it was machine-drafted.

Start a book Read the source

Claude Code · Codex CLI · Grok Build · Agy · Cursor · Cline · Aider

READINESS · PASS

DRAFTS / CH07 · VOICE LOCKED · REV 3

She knew exactly why she had come back to the harbor — not merely for the sea, but for the version of herself she had left on it.

Marta walked the pier. It wasn’t just the salt air; it was the memories that seemed to seep from the very boards beneath her feet. The boards had memory in them, she thought — her grandmother’s, mostly, and one wet August that was hers alone.

critic, pass 3 — “seep from the very boards” is tell № 14. Ground it in a real August. — revised below, rescored 8.1

The method

A pipeline, not a prompt.

Frontier models write good sentences. Left alone they still write books readers put down. None of that is a model problem — it is a pipeline problem — and Velith is the pipeline.

0Onboardingreader, promise, scope — and a voice fingerprint from your own writing 1Ideationpremise stress-tested against real comparable titles; you choose 2Outliningstructure chosen and justified, chapter specs, the book bible 3Draftingvoice locked on a sample, then full-context chapters, critiqued and revised 4Editingfact check, developmental, line, copy, proofread — rewritten in place 5PublishingEPUB / PDF / MOBI, epubcheck, cover from the art bible

Why books fail

What readers actually notice.

Velith’s quality bar is built on the 2026 AI-tell taxonomy — the things that put readers down now, not the “delve” lists of two years ago.

A voice that drifts by chapter eight, because each chapter was written without the ones before it
Characters who explain their feelings instead of having them
Statistics and citations that do not exist
Paragraphs that all end on a punch line, in a rhythm readers feel before they name
“Not X but Y” constructions every other page
Illustrations that change style every chapter

Agents receive chapter summaries.

Every agent reads the entire manuscript. Frontier models carry a million tokens; a novel is under 200K. Summaries are what made the voice drift.

One pass per chapter, saved as-is.

Draft → cold critique with quoted lines → revise — before the file is ever saved.

Editing produces reports.

Editing rewrites the manuscript in place, with snapshots, across seven stages.

“Files exist” counts as done.

Publishing is gated by simulated readers: three target readers and one genre professional cold-read the book. Every axis ≥ 7, no put-down point in the first three chapters — or the verdict is REVISE.

The gate

Five axes. Scored honestly. Published only above the line.

The same rubric every writing, editing, and reviewing agent reads. Voice lock needs axis one at 7 or better. Publication needs all five.

Voice & prosereadiness needs ≥ 7

Structure & pacing≥ 7

Depth≥ 7

Specificity & grounding≥ 7 — the fact-checker’s ledger feeds this

Reader experience≥ 7, mean ≥ 7.5

| = the publishing gate. Below it, the verdict is REVISE and the loop runs again.

Dramatis personae

Twelve specialists, one shared standard.

Skills are the entry points; these are the agents behind them. Each has a minimal toolset and its own effort level — the writer and the beta reader get the most.

book-architectChooses and justifies the structure, scores the outline, proposes restructures.

scene-generatorPlans every fiction scene — purpose, turn, subtext, exit hook. Plans, never prose.

chapter-writerDrafts one chapter in full context; critiques itself with quoted lines; revises.

continuity-editorHunts contradictions and repetitions across the whole manuscript against the bible.

fact-checkerBuilds a claim ledger; verifies against sources and the web; removes what it can’t verify.

style-doctorMeasures rhythm, tells, and drift with real metrics — then rewrites in place.

beta-readerCold-reads as three target readers and one professional; issues the verdict.

art-directorOwns the one look per book: art bible, look lock, vision QA on every image.

figure-engineerRenders diagrams, charts, and drawings from code — labels verified against the text.

illustratorIllustrations from compiled art-bible prompts, for whichever image model you have.

cover-designerCover concepts from the art bible — ebook, print wrap, audiobook, marketing.

marketing-expertPositioning, comparable-title framing, channels, and the launch calendar.

Usage

Two commands start the book. /loom runs the rest.

You approve at the author checkpoints — concept, outline, voice lock, look lock, readiness. Everything between them runs unattended.

In Claude Code

/plugin marketplace add epicsagas/plugins
/plugin install velith@epicsagas

# in your empty book directory
> /book-init   # genre, reader, voice sample → PRD + STYLE
> /loom        # detects state, runs the next phase, stops at checkpoints

Eighteen skills ship with the plugin, including seven genre craft references — fiction, non-fiction, technical, screenplay, poetry, game, academic — and a custom genre builder.

On the command line

node velith.mjs scan my-book --ui
node velith.mjs metrics drafts/ch07.md
node velith.mjs snapshot my-book pre-lineedit
node velith.mjs images compile my-book
node velith.mjs images render my-book

Deterministic prose metrics (sentence rhythm, tell density, cross-chapter repetition), snapshots before every rewriting stage, and per-backend image prompts. /book-status --ui opens the Svelte dashboard.

The Velith dashboard: pipeline tracker, agent cards, chapter table, editing stages, readiness verdict

Compared

Against the alternatives.

	Velith	Raw prompts	Notion AI	Jasper / Sudowrite	Scrivener
Full-manuscript context	Every agent, every task	Manual	None	Limited	n/a
Voice lock + critique loop	Built in	None	None	None	Manual
Fact-checking, claim ledger	Dedicated agent	None	None	None	Manual
Readiness gate by cold readers	Blocks publishing	None	None	None	None
Visual consistency per book	Art bible + vision QA	Per-image prompts	None	None	None
Output	EPUB, PDF, MOBI, TXT, MD	Copy-paste	Markdown / PDF	DOCX, limited	DOCX, PDF
Control	Prompt-level, Apache-2.0	Full	Black box	Black box	Full

The reader never has to know. The writer always does.

Start with onboarding and a page of your own prose — the voice fingerprint does the rest.

Install Velith Launch playbook