ledgerbound

Check a chapter of a Ledgerbound novel against the record (stats, items, time, location, knowledge) and against its plan, in a fresh subagent that did not write it. Use for one chapter on request; verify-chapter runs it as part of every check.

Check prose against guidelines/writing.md in a fresh subagent that did not write it - lint plus judged rules (endings, dialogue, subtext, emotion, voice cards). Use for a voice sample, a chapter draft, or any prose file in a Ledgerbound novel repo.

Grow a one- or two-sentence LitRPG / progression-fantasy idea into three complete premises, align with the user on what to include and exclude when none fits, then develop the chosen one into pitch.md for start-project. Use when the user has only a short idea, or start-project finds the material too thin.

Write the rest of a Ledgerbound book chapter by chapter, and continue after a usage-limit stop or a closed session from the files in runs/. Use when the user wants the whole book, or asks to continue or resume a run.

Write one chapter of a Ledgerbound novel end to end - brief, delta, prose, verification, approval, rolling memory and a git commit. Use for the next chapter, or when the user names one (for example 1.07).

Intake for a series whose book 1 the author already wrote without Ledgerbound - splits the manuscript into chapters, reads it, and makes the story bible, schema, facts, rolling memory, lore, characters and the book-1 plan from it, so that the tool writes book 2 and later. Use when the user has a written or published book to continue, or `lb status` names import-book.

Character arcs, voice cards and relationships for a planned LitRPG story - want, need, lie, wound, contradiction, how each character speaks in each emotional state, arc beats mapped to acts and books, how the voice changes with the arc, and how the main characters are together (romance included) and how that changes. Use after the book plans are approved, or when `lb status` names plan-arcs.

Chapter and scene plans for the next LitRPG book to write - each chapter's job, tension and stakes, threads, arc beats, relationship stages, bonding chapters, ending type and scenes with their results, plus threads.yaml. Use after the character arcs are approved, or when `lb status` names plan-book.

Plan a LitRPG series or book from the end, top down - series ending, then every book at book level with its acts, climax and tension range, then the progression targets. Use after the bible is approved, or when `lb status` names plan-series.

World planning for a LitRPG story - lore entries for its places, factions, history, customs, laws, creatures, and how the System works in the world. Use after the story bible is approved, when `lb status` names plan-world, or when the user wants to add or change lore.

Make a complete Ledgerbound book ready to publish - the publish file (metadata, blurb, keywords), the front and back pages, and an EPUB from `lb export`. Use when a book is done and the user wants to publish it, or wants an EPUB of a book to read or share (a draft export).

Change the rest of a Ledgerbound plan when the draft moves away from it - the unwritten chapter plans, threads, targets, anchors and open decisions - and get the user's approval. Use when `lb commit` reports REPLAN NEEDED, when verify-chapter returns replan or blocked on a plan error, or when the user wants to change the direction of the story.

Intake for a new LitRPG / progression-fantasy novel or series. Turns what the user has (plot, style, POV, characters, setting, stat system, or a pitch.md) into a story bible, schema and facts. Use when the user starts a new story, or `lb status` names start-project.

Check one chapter of a Ledgerbound novel with the prose-checker and continuity-checker agents at the same time, then revise only the flagged spans, for at most 3 rounds. Use after a chapter is drafted, or when `lb run` names verify-chapter.

Write and approve the three voice samples (a dialogue, an action and a quiet scene, ~500 words each) that become the prose reference for a LitRPG project, and fix the status-window template. Use after the chapter plans are approved, or when `lb status` names voice-sample.