The short version: if you are doing obsidian novel writing in 2026, you probably have templates for notes, tasks and second brains — but nothing for the mechanics of finishing and submitting a novel. WriterVault is a 20-file Obsidian manuscript and story-bible vault: chapter log, scene cards, continuity guards, submission tracker, zero required plugins. It is listed at a $1 intro price at the time of writing, and it is writing structure, full stop.
You live in Obsidian: your notes, tasks and half-ideas are plain Markdown on your own disk. Your novel is not: it lives in three places at once, a folder of chapter drafts whose filenames stopped matching reality in April, notes where the harbour city keeps changing size between books, and an inbox where agent queries go to be forgotten.
The search data points at that gap too. In a 2026 sweep of Google autocomplete, 34 of 34 writer, novelist and manuscript seed phrases completed with Obsidian-specific intent: "obsidian writer" toward vault, setup, template; "obsidian novel writing" toward template, plugin, software, setup; "obsidian for writers" toward templates, vault, setup. People keep typing "vault for writers" in slightly different words.
One honest caveat: autocomplete completions are partly learning intent — typing a phrase to see what exists is not proof of purchase intent. We read this as a question being asked, not a market settled. What we can say is narrower: the direct paid lane is thin and unrated at the direct level, the free worldbuilding vaults exist and are genuinely good, and neither covers the manuscript pipeline. Both, honestly, below.
What the existing options actually cover
We like the free vaults. It is still worth being precise about the layers: "an Obsidian template for writers" can mean three different things.
| Capability | Free worldbuilding vaults | General Obsidian templates | WriterVault |
|---|
| Worldbuilding and notes structure | Strong — that is their point | Decent capture | Dossiers, guards, series canon log |
| Chapter pipeline (idea to locked) | Rare | Rare | Closed five-word ladder, rolling word counts |
| Scene-level word reconciliation | No | No | Scene cards sum to the chapter total |
| Submission tracker | No | No | Eight-column log plus response-time math |
| Series continuity (book-two drift) | Partial | No | Series canon log (C-##), referenced not remembered |
| Zero required plugins | Varies | Dataview-centric | Yes — plain pipe tables, plain text friendly |
The middle column is why we stopped patching our own vault: general templates are built for note capture, and a novel is not a note — it is a pipeline with states, counts and a paper trail.
Two conventions you can steal today, kit or no kit
Nothing here requires WriterVault or a purchase — if these two conventions alone fix your mess, take them and go.
1. The five-word status ladder
Every chapter row in your chapter log carries exactly one of five status words from a closed vocabulary — for example: idea, drafted, revised, line-edited, locked. Five words, no synonyms, no sixth word ever.
The closed ladder is the whole trick. It is what lets a plain Markdown table answer the only question that matters mid-draft: what is actually done? Open-ended statuses break this instantly. "Needs work" and "almost there" are not states, they are feelings, and a table of feelings is unqueryable. With five fixed words you can scan the column and know eleven chapters are locked and three are still at drafted — and your word-count column answers what is locked, not just what exists.
2. Continuity guards
One note per locked fact, numbered CG-01, CG-02 and on. Write each guard in present tense with concrete numbers only: "The harbor city of Vess has 40,000 residents" — not "a big city". Numbers are checkable; adjectives drift.
The rule that makes it work: when a scene contradicts a guard, you fix the scene, never the guard. This sounds pedantic until book two, when the character whose mother died in book one is calling her on page forty. Guards turn continuity from a memory test into a lookup.
Make it a two-minute check before every revision pass: read the guards that apply to the chapters you are about to touch. Two minutes against a week of silent drift is the best trade in this post.
WriterVault: twenty files that make the pipeline visible
WriterVault — The Obsidian Manuscript & Story-Bible Vault — is exactly 20 Markdown files. It is an Obsidian manuscript workflow, not a pile of prompts: copy the files into your vault, or any Markdown folder, and the structure does its work in stock Obsidian.
The chapter log, as a manuscript tracker
The chapter log carries the closed five-word ladder and a word-count column that rolls up to the whole book. The canonical chapter row is a plain pipe table — this is literally the format:
| Ch | Title | POV | Status | Words | Last edited |
No plugin reads it — you do, or any Markdown editor, or a plain text file in ten years.
Scene cards that reconcile
Each scene gets a card with an SC-### id and a word count, and a chapter's scenes sum exactly to that chapter's number in the log. If chapter twelve says 3,100 words and its cards add to 2,950, something is wrong — and you find out now, while it is one chapter, not at compile time with the whole book.
Dossiers, guards, and a series bible
Character dossiers sit beside the continuity guards (CG-##) from the free method above, and series writers get a series canon log (C-##): facts that must stay true across books, recorded once and referenced instead of remembered. That is the direct answer to book-two drift.
The submission tracker
Every query you send becomes a row under an eight-column contract:
| ID | Date Sent | Target | Type | Material | Status | Response Date | Response Days |
On top of the log sits response-time math: average, median, fastest, slowest, request rate, days open. This is the "turn agent silence into numbers" part. A silent inbox becomes a row with a date, and a pile of rows becomes arithmetic. To be explicit: this tracks your own sending. It sends nothing, finds no agents, and predicts no replies.
Dashboards, query skeleton, offline compile
The kit includes two weekly dashboards built from the same tables — one for where the manuscript stands, one for where the submissions stand — a query-letter skeleton, and an offline pandoc compile recipe that assembles your chapter files into one .docx manuscript file. No accounts, no network calls.
Zero required plugins
Everything above runs on standard pipe tables: stock Obsidian, any Markdown editor, or plain text in a folder. Six Dataview queries ship as a clearly marked OPTIONAL bonus — if you love Dataview, use them; nothing depends on them. No accounts, and nothing leaves your device.
The worked example is a full fictional sample novel
A blank template is easy to ship; a finished example that adds up is what teaches. The kit ships one, all FICTIONAL SAMPLE DATA: a fictional writer, Wren Calloway, and her fictional novel The Salt Cartographer. It has 24 chapters and 69,080 words — 76.8% of a 90,000-word target (FICTIONAL SAMPLE DATA) — with scene cards summing exactly to their chapters and a 12-row submission log where every response-day cell is exact calendar arithmetic (FICTIONAL SAMPLE DATA). None of it describes a real writer or agency; it exists so you can watch every rollup reconcile before trusting the empty templates with your own draft.
The honest competition section
Two things compete with this kit, and both deserve straight words.
- The Novelist (free Obsidian vault, rated 5.0 out of 12) is genuinely good at worldbuilding and notes structure. If worldbuilding is what you need, take it — it is free and it works. The wedge here is a different layer of the job: manuscript pipeline, submission tracker, series continuity.
- Writer & Knowledge OS ($15, zero ratings) is the direct paid rival, and it owns the direct keyword — search it and you will find it before us. We differentiate on depth and workflow, as described above, not on being first.
Gumroad's writer-product culture leans heavily pay-what-you-want, and plenty of good vaults are priced that way. This one uses a $1 intro price with a price ladder behind it instead — the ladder rises as sales milestones hit, and we would rather say so than hide it.
Who it is NOT for
We would rather you skip it than buy the wrong thing.
- Writers who want software that writes or edits the book. This is writing structure only. It is not AI, not an agent-finder, not a submission service. It does not write, edit, market or pitch your novel; you do all of that, in your files, on your device.
- Writers happy in Scrivener with no interest in plain files. Scrivener is a good program, and if its corkboard is where your novel lives, a folder of Markdown will feel like a downgrade.
- Anyone expecting a guarantee of publication, representation or income. No structure offers that, and anyone selling you one is describing a feeling, not a feature. The kit is writing structure, full stop.
Disclosure and the product page
Disclosure: this post links to a product we made. If you buy through it, we may earn a commission at no extra cost to you.
Product page: WriterVault — The Obsidian Manuscript & Story-Bible Vault on Gumroad.
Get the kit
WriterVault is listed at a $1 intro price at the time of writing — we confirmed that on 2026-10-25 against the live page. It is an intro price with a price ladder behind it, so it may rise as sales milestones hit, and we cannot promise it stays at $1.
Get WriterVault on Gumroad.
What it gives you is structure for a manuscript and a submission pipeline, in plain files that stay on your device — all it gives you, and all it claims to.
Wrapping up
If you want an obsidian novel writing workflow that treats your book as a pipeline — a chapter log that answers "what is actually done?", scene cards that reconcile, guards against book-two drift, a submission log that turns silence into numbers — WriterVault is the 20-file vault we built for it. The product page is right here.
Corrections and questions are welcome — if we got a fact wrong or a convention is missing something you use, write to nandminc2020@gmail.com and we will fix it.
Keep reading
Comments
Post a Comment