Scriven has 108 commands organized into 14 categories. Commands adapt automatically to your work type -- for example, /scr:draft talks about drafting a surah for Quranic commentary, an act for screenplays, and a section for research papers.
Commands marked with adaptive terminology change how Scriven talks about your work type's command_unit in .manuscript/config.json, while keeping the runnable command id stable. Commands marked with group adaptation have different labels for specific work type groups (academic, sacred, etc.).
- Core -- The main workflow: create, discuss, plan, draft, review, submit
- Navigation -- Find your way: next step, help, progress, import
- Session -- Save, compare, undo, pause and resume your work
- Structure -- Plot graphs, timelines, themes, outlines
- Structure Management -- Add, insert, remove, split, merge, reorder units
- Character & World -- Characters, relationships, world-building
- Quality -- Voice calibration, line editing, copy editing, polish
- Review -- Continuity, voice, sensitivity, pacing, dialogue, beta readers
- Publishing -- Front/back matter, blurbs, synopses, export, publish
- Illustration -- Cover art, scene illustrations, character refs, maps
- Translation -- Translate, glossary, memory, cultural adaptation
- Collaboration -- Revision tracks and their collaboration subcommands
- Utility -- Manager, health checks, quick edits, notes, settings
- Sacred Exclusive -- Concordance, cross-reference, genealogy, and more
The main workflow commands. Every writing project follows this chain: new-work, discuss, plan, draft, editor-review, submit, complete-draft.
Description: Start a new creative work. Adaptive onboarding detects work type and generates tailored context files.
Usage: /scr:new-work [--quick] [--type <work_type>]
Prerequisites: None
Flags:
--quick-- Skip questions 2-3, use defaults--type <work_type>-- Skip the "what are you writing?" question
Example:
/scr:new-work --type novel
Start a novel project. Scriven asks your premise and whether you have existing material, then generates all context files.
Description: Shape the next unit before planning. Discuss the approach, voice, themes, open questions.
Usage: /scr:discuss [unit number]
Prerequisites: OUTLINE.md must exist
Adaptive terminology: Scriven keeps the runnable command as /scr:discuss and frames the unit appropriately -- chapter (novel), act (screenplay), surah (Quranic), section (research paper)
Example:
/scr:discuss 3
Talk through Chapter 3 before planning it -- themes to explore, character arcs to advance, tone shifts to consider.
Description: Research and plan the next unit. Produces a structured plan file the drafter agent uses.
Usage: /scr:plan [unit number]
Prerequisites: Discussed unit context ({N}-CONTEXT.md)
Adaptive terminology: Same pattern as discuss -- /scr:plan stays stable while Scriven speaks in chapters, acts, surahs, and other unit labels
Example:
/scr:plan 5
Research and plan Chapter 5, producing plan files for each scene the drafter agent will use.
Description: Draft the planned unit. Invokes the drafter agent in fresh context per atomic unit.
Usage: /scr:draft [unit number]
Prerequisites: Plan files must exist ({N}-*-PLAN.md)
Adaptive terminology: /scr:draft stays stable while Scriven frames the work as drafting a chapter, act, surah, section, and so on
Example:
/scr:draft 5
Draft all scenes in Chapter 5. Each scene gets fresh context with STYLE-GUIDE.md loaded first to maintain your voice.
Description: Walk the writer through editorial review, manage editor-writer collaboration workflow with proposal reviews, notes, and decision tracking.
Usage: /scr:editor-review [N] [--proposal <name> | --notes | --respond <name>]
Prerequisites: Draft files must exist in .manuscript/drafts/body/ ({N}-*-DRAFT.md)
Flags:
--proposal <name>-- Review a specific editorial proposal--notes-- View editor notes--respond <name>-- Respond to an editor proposal
Group adaptation:
- Academic label:
peer-review - Sacred label:
scholarly-review
Example:
/scr:editor-review 3
Review the draft of unit 3 with your editor hat on. Scriven highlights issues, suggests improvements, and tracks your decisions.
Description: Package and finalize unit.
Usage: /scr:submit [unit number]
Prerequisites: Editor notes must exist ({N}-EDITOR-NOTES.md)
Adaptive terminology: /scr:submit stays stable while Scriven describes the current chapter, act, surah, or other unit being finalized
Example:
/scr:submit 3
Finalize Chapter 3 after editor review. Marks it as complete in the workflow.
Description: Mark the entire manuscript draft as complete.
Usage: /scr:complete-draft
Prerequisites: All units must be submitted
Example:
/scr:complete-draft
After all chapters are submitted, mark the full draft as complete. Unlocks publishing, export, and translation commands.
Description: Start a new revision of the manuscript. Archives the current draft and begins a fresh pass.
Usage: /scr:new-revision
Prerequisites: Archived draft must exist
Example:
/scr:new-revision
Archive the current draft and start revision 2. All drafts are preserved in the archive.
Description: Run the full drafting pipeline autonomously. Choose guided, supervised, or full-auto profiles.
Usage: /scr:autopilot [--profile guided|supervised|full-auto] [--from <stage>] [--to <stage>] [--unit N] [--resume]
Prerequisites: None (recommended: run /scr:profile-writer first)
Flags:
--profile-- Control level:guided(pauses for approval),supervised(pauses at milestones),full-auto(runs everything)--from/--to-- Limit the pipeline stages--unit N-- Start from a specific unit--resume-- Continue from where autopilot left off
Example:
/scr:autopilot --profile supervised --from plan --to draft
Run planning and drafting for all units, pausing at milestones for your review.
Description: Create, view, or check the series bible -- a persistent cross-book knowledge base for multi-volume works (novel series, TV seasons, comic runs, sequel trilogies, multi-book commentaries).
Usage: /scr:series-bible [--init] [--import <work_path>] [--check] [--timeline] [--characters]
Prerequisites: None
Flags:
--init-- Create a new series bible--import <work_path>-- Import from an existing work--check-- Verify consistency across volumes--timeline-- Show series-wide timeline--characters-- Show character appearances across volumes
Example:
/scr:series-bible --init
Start a series bible for a trilogy. Track characters, world details, and timelines across all books.
Commands for finding your way through the workflow and understanding your manuscript.
Description: Auto-detect what to do next in your workflow and run it. The one command a writer can always use.
Usage: /scr:next
Prerequisites: None
Example:
/scr:next
Not sure what comes after planning? Just run /scr:next and Scriven figures it out.
Description: Natural language router. Type what you want in plain English, Scriven figures out which command to run.
Usage: /scr:do "<what you want to do>"
Prerequisites: None
Example:
/scr:do "edit the scene where Maria meets the detective"
Scriven maps your intent to the right command and runs it.
Description: Show Scriven commands grouped by workflow stage, filtered to what's relevant for your current work type and progress.
Usage: /scr:help [category or search term]
Prerequisites: None
Example:
/scr:help publishing
Show all publishing-related commands available for your work type.
Description: Show current state and next step. How far along are you, what's drafted, what's pending.
Usage: /scr:progress
Prerequisites: None
Example:
/scr:progress
See "Chapter 4 of 12 drafted. 32,000 words. Next: discuss-chapter 5."
Description: Launch or clear a pre-built sample project sandbox for exploring Scriven without risk.
Usage: /scr:demo [--clear] [--genre <genre>]
Prerequisites: None
Flags:
--clear-- Remove the demo project--genre <genre>-- Choose a demo genre
Example:
/scr:demo
Explore Scriven with a pre-built watchmaker story -- 5 scenes, full context files, everything ready to try commands.
Description: Import an existing manuscript (docx, markdown, txt, or directory) and structure it into a Scriven .manuscript/ directory.
Usage: /scr:import <file_or_directory_path> [--type <work_type>]
Prerequisites: None
Flags:
--type <work_type>-- Specify the work type if Scriven can't auto-detect it
Example:
/scr:import ~/Documents/my-novel.docx --type novel
Import an existing Word document and split it into chapters, scenes, and context files.
Description: Spawn parallel analysis agents to understand an existing manuscript's voice, structure, characters, and themes.
Usage: /scr:map-manuscript
Prerequisites: None
Example:
/scr:map-manuscript
Analyze a manuscript you imported. Scriven reads the whole thing and extracts voice profile, character list, themes, and structure.
Description: Show manuscript word count, page count, unit count, and reading time -- with progress against your work type's industry-standard ranges.
Usage: /scr:manuscript-stats [--detail]
Prerequisites: None
Flags:
--detail-- Show per-unit breakdown
Output includes:
- Total words and pages vs. work type target range (e.g., 14,200 / 70,000–100,000 words)
- Units drafted vs. expected count (e.g., 4 / 20–35 chapters)
- Per-unit pacing check against unit word/page range
- Estimated reading time
Word and page ranges are sourced from word_count_range, page_range, unit_count_range, unit_word_range, and unit_page_range in CONSTRAINTS.json. Page counts use ~250 words/page (standard manuscript format).
Example:
/scr:manuscript-stats --detail
See word counts per chapter, total pages, progress against targets, and estimated reading time.
Writer-friendly git abstractions. Save your work, compare versions, and undo mistakes -- no git knowledge required.
Description: Save your current work. Auto-generates a descriptive save message from context.
Usage: /scr:save [optional message]
Prerequisites: None
Example:
/scr:save "finished the rooftop confrontation"
Save your work with a note. If you skip the message, Scriven writes one based on what changed.
Description: See the timeline of your saves. Shows when you saved and what you were working on.
Usage: /scr:history [--limit N]
Prerequisites: None
Flags:
--limit N-- Show only the last N saves
Example:
/scr:history --limit 5
See your last 5 saves with timestamps and descriptions.
Description: Compare your current work with a previous save. Shows changes in plain prose, not code diff.
Usage: /scr:compare [save number or 'last']
Prerequisites: None
Example:
/scr:compare last
See what changed since your last save, described in plain language.
Description: List your draft versions with readable labels.
Usage: /scr:versions [--all]
Prerequisites: None
Flags:
--all-- Remove the default 10-version limit and show the complete save-version list
Example:
/scr:versions
See your recent save timeline with readable labels like "Current", "Yesterday", and "Apr 4".
Use --all when you want the complete save-version list without the default 10-version cap.
Description: Undo your last save and go back to the previous version.
Usage: /scr:undo [--force]
Prerequisites: None
Flags:
--force-- Skip the unsaved-changes warning, but still require confirmation before undoing
Example:
/scr:undo
Go back to the previous save. Scriven shows what will be reverted and still asks for confirmation, even with --force.
Description: Pause your work session. Captures where you are and what you were thinking so you can pick up later.
Usage: /scr:pause-work
Prerequisites: None
Example:
/scr:pause-work
Capture your mental state before stepping away. Scriven notes what you were working on, open threads, and next steps.
Description: Pick up where you left off. Reads your last session and tells you what's next.
Usage: /scr:resume-work
Prerequisites: None
Example:
/scr:resume-work
Get oriented after a break. Scriven reminds you what you were doing and suggests what to tackle next.
Description: See what you accomplished this session. Shows units drafted, words written, and time spent.
Usage: /scr:session-report
Prerequisites: None
Example:
/scr:session-report
End-of-session summary: "You drafted 3 chapters (8,400 words) over 2.5 hours. Voice consistency: 94%."
Commands for visualizing and managing your narrative structure, themes, and timeline.
Description: Visualize and manage the narrative arc structure of the story.
Usage: /scr:plot-graph [--edit] [--type <arc_type>]
Prerequisites: OUTLINE.md must exist
Flags:
--edit-- Modify the arc structure--type <arc_type>-- Arc type: three-act, five-act, hero's journey, kishotenketsu, etc.
Available for: Prose, script, visual, interactive
Group adaptation:
- Technical label:
procedure-map
Example:
/scr:plot-graph --type hero's-journey
Visualize your novel's structure mapped to the hero's journey.
Description: Generate a chronological event timeline from the outline.
Usage: /scr:timeline
Prerequisites: OUTLINE.md must exist
Available for: Prose, script, academic, visual, interactive
Sacred note: Sacred projects use the dedicated /scr:sacred:chronology command instead of /scr:timeline.
Example:
/scr:timeline
See events in chronological order, even if your narrative is non-linear.
Description: Track thematic threads across the work with auto-detection suggestions.
Usage: /scr:theme-tracker
Prerequisites: THEMES.md must exist
Available for: Prose, script, visual, poetry, interactive
Example:
/scr:theme-tracker
See where your themes appear across chapters and which ones need more development.
Description: Visualize subplot threads and their intersections across the work.
Usage: /scr:subplot-map
Prerequisites: OUTLINE.md must exist, at least 2 threads
Available for: Prose, script, interactive
Example:
/scr:subplot-map
See how your subplots weave together and where they intersect with the main plot.
Description: Display or edit the structural outline of the work.
Usage: /scr:outline [--edit]
Prerequisites: OUTLINE.md must exist
Available for: Prose, script, academic, visual, interactive, sacred
Flags:
--edit-- Modify the outline
Example:
/scr:outline --edit
View and restructure your outline interactively.
Commands for modifying the structural units in your outline -- adding, removing, splitting, merging, and reordering.
Description: Add a new unit to the end of the outline.
Usage: /scr:add-unit [title]
Prerequisites: OUTLINE.md must exist
Available for: Prose, script, academic, visual, interactive, sacred
Example:
/scr:add-unit "The Aftermath"
Add a new chapter (or act, section, surah, etc.) at the end of the outline.
Description: Insert a new unit at a specific position in the outline.
Usage: /scr:insert-unit [position] [title]
Prerequisites: OUTLINE.md must exist
Available for: Prose, script, academic, visual, interactive, sacred
Example:
/scr:insert-unit 3 "The Reveal"
Insert a new chapter at position 3, shifting later chapters forward.
Description: Remove a unit from the outline with draft safety checks.
Usage: /scr:remove-unit [unit-id]
Prerequisites: OUTLINE.md must exist
Available for: Prose, script, academic, visual, interactive, sacred
Example:
/scr:remove-unit 7
Remove chapter 7. Scriven warns if it has drafted content and asks for confirmation.
Description: Split one unit into two at a specified point.
Usage: /scr:split-unit [unit-id] [split-point]
Prerequisites: OUTLINE.md must exist
Available for: Prose, script, academic, visual, interactive, sacred
Example:
/scr:split-unit 5 "after the trial scene"
Split Chapter 5 into two chapters at the specified point.
Description: Merge two adjacent units into one.
Usage: /scr:merge-units [unit-id-1] [unit-id-2]
Prerequisites: OUTLINE.md must exist
Available for: Prose, script, academic, visual, interactive, sacred
Example:
/scr:merge-units 3 4
Merge chapters 3 and 4 into a single chapter.
Description: Reorder units in the outline by moving a unit to a new position.
Usage: /scr:reorder-units [unit-id] [new-position]
Prerequisites: OUTLINE.md must exist
Available for: Prose, script, academic, visual, interactive, sacred
Example:
/scr:reorder-units 8 3
Move chapter 8 to position 3, shifting other chapters accordingly.
Commands for creating and managing characters, relationships, and world-building. Hidden for poetry and speech work types.
Description: Build a complete character profile through guided interactive interview.
Usage: /scr:new-character
Prerequisites: WORK.md must exist
Available for: Prose, script, visual, interactive
Example:
/scr:new-character
Start building a character. Scriven interviews you about appearance, personality, backstory, voice, and role in the story.
Description: Display or edit a specific character's full profile.
Usage: /scr:character-sheet [name] [--edit]
Prerequisites: CHARACTERS.md must exist
Available for: Prose, script, visual, interactive
Flags:
--edit-- Modify the character profile
Example:
/scr:character-sheet Maria --edit
View Maria's full profile and make changes.
Description: Generate an ASCII relationship graph between characters.
Usage: /scr:relationship-map [--edit]
Prerequisites: CHARACTERS.md must exist with at least 2 characters
Available for: Prose, script, visual, interactive
Flags:
--edit-- Modify relationships
Example:
/scr:relationship-map
See how all your characters relate to each other in an ASCII diagram.
Description: Generate or refine the world document through progressive questioning.
Usage: /scr:build-world [--area <area>]
Prerequisites: None
Available for: Prose, script, technical, visual, interactive
Group adaptation:
- Technical label:
map-system
Flags:
--area <area>-- Focus on a specific area of the world
Example:
/scr:build-world --area "magic system"
Flesh out your magic system through guided world-building questions.
Description: Display the roster of all characters with roles and brief descriptions.
Usage: /scr:cast-list
Prerequisites: None
Available for: Prose, script, visual, interactive
Example:
/scr:cast-list
Quick overview of all characters: name, role, one-line description.
Description: Visualize a character's emotional and growth arc across the story.
Usage: /scr:character-arc [name]
Prerequisites: CHARACTERS.md must exist
Available for: Prose, script, visual, interactive
Example:
/scr:character-arc Maria
See Maria's emotional journey mapped across chapters -- where she starts, key turning points, where she ends.
Description: Generate a dialogue sample to preview a character's voice before drafting.
Usage: /scr:character-voice-sample [name]
Prerequisites: CHARACTERS.md and STYLE-GUIDE.md must exist
Available for: Prose, script, visual, interactive
Example:
/scr:character-voice-sample Detective Chen
Hear how Detective Chen sounds in dialogue before you start drafting scenes with them.
Commands for calibrating voice and polishing prose.
Description: Voice calibration gate. Generates a 300-word passage in the writer's proposed voice and asks "does this sound like you?" before any real drafting begins.
Usage: /scr:voice-test
Prerequisites: None
Available for: All work types
Example:
/scr:voice-test
Scriven drafts a sample passage using your voice profile. If it doesn't sound right, you refine together until it does.
Description: Perform a line-level prose quality pass with inline annotations.
Usage: /scr:line-edit
Prerequisites: Draft must exist
Available for: All work types
Example:
/scr:line-edit
Scriven reads your prose line by line, flagging weak verbs, passive voice, redundancy, and awkward phrasing.
Description: Perform a correctness pass for grammar, spelling, punctuation, and consistency.
Usage: /scr:copy-edit
Prerequisites: Draft must exist
Available for: All work types
Example:
/scr:copy-edit
Catch typos, grammar issues, and consistency problems (character name spellings, timeline errors, style inconsistencies).
Description: Chain line-edit, copy-edit, and voice-check for comprehensive prose polish.
Usage: /scr:polish
Prerequisites: Draft and STYLE-GUIDE.md must exist
Available for: All work types
Example:
/scr:polish
Run all three quality passes in sequence. The comprehensive final polish before publication.
Description: Write a scene, passage, or chapter outside the full planning workflow.
Usage: /scr:quick-write
Prerequisites: None
Available for: All work types
Example:
/scr:quick-write
Skip the plan-then-draft workflow and just write. Good for inspiration strikes or experimental scenes.
Commands for reviewing your manuscript from different angles -- continuity, voice, sensitivity, pacing, dialogue, and reader experience.
Description: Automated continuity verification to scan for narrative contradictions across the manuscript.
Usage: /scr:continuity-check
Prerequisites: Draft must exist
Available for: Prose, script, visual, interactive
Group adaptation:
- Technical label:
consistency-check
Example:
/scr:continuity-check
Find contradictions: "In Chapter 3 Maria has brown eyes, but in Chapter 7 they're green."
Description: Compare drafted prose against STYLE-GUIDE.md to detect voice drift.
Usage: /scr:voice-check
Prerequisites: Draft and STYLE-GUIDE.md must exist
Available for: All work types
Group adaptation:
- Sacred label:
register-check(voice register consistency)
Example:
/scr:voice-check
Detect where your drafted prose drifts from your established voice profile.
Description: Flag potential sensitivity issues with context, suggest alternatives, and note intentional craft.
Usage: /scr:sensitivity-review
Prerequisites: Draft must exist
Available for: All work types
Group adaptation:
- Academic label:
ethics-review - Sacred label:
interfaith-review(sensitivity across traditions)
Example:
/scr:sensitivity-review
Flag content that could be unintentionally harmful, with context-aware suggestions that respect your creative intent.
Description: Generate a structure-aware pacing report analyzing scene tempo and narrative flow.
Usage: /scr:pacing-analysis
Prerequisites: Draft must exist
Available for: Prose, script, academic, visual, interactive, sacred
Example:
/scr:pacing-analysis
See where your story drags or rushes. Scriven maps scene length, tension, and tempo across the full manuscript.
Description: Audit dialogue for character voice differentiation, attribution clarity, and talking-head detection.
Usage: /scr:dialogue-audit
Prerequisites: Draft must exist with dialogue
Available for: Prose, script, interactive
Group adaptation:
- Visual: adapted behavior for balloon text analysis
Example:
/scr:dialogue-audit
Check that each character sounds distinct, dialogue tags are clear, and scenes aren't just talking heads.
Description: Simulate a beta reader's experience of the manuscript with cross-AI peer review.
Usage: /scr:beta-reader
Prerequisites: Draft must exist
Available for: All work types
Group adaptation:
- Academic label:
reviewer-simulation - Sacred label:
theological-review(doctrinal/pastoral review)
Example:
/scr:beta-reader
Get a simulated reader's reaction: what hooked them, where they got confused, what felt slow, what surprised them.
Description: Scan drafted prose for AI-generated patterns and unintentional similarity to published works.
Usage: /scr:originality-check
Prerequisites: Draft must exist
Available for: All work types
Example:
/scr:originality-check
Flag passages that feel generic or accidentally echo published works.
Commands for preparing your manuscript for publication -- front/back matter, marketing copy, export formats, and publishing workflows.
Description: Generate publication-ready front matter elements in Chicago Manual of Style order.
Usage: /scr:front-matter
Prerequisites: Complete draft must exist
Available for: Prose, script, academic, visual, sacred
Group adaptation:
- Academic: adapted behavior for academic front matter (abstract, acknowledgments, etc.)
- Sacred: adapted behavior for sacred front matter (imprimatur, dedication to deity, etc.)
Example:
/scr:front-matter
Generate title page, copyright page, dedication, epigraph, table of contents, and more.
Description: Generate publication-ready back matter elements.
Usage: /scr:back-matter
Prerequisites: Complete draft must exist
Available for: Prose, script, academic, visual, sacred
Group adaptation:
- Academic: adapted behavior for academic back matter (bibliography, appendices, etc.)
- Sacred: adapted behavior for sacred back matter (glossary of terms, concordance index, etc.)
Example:
/scr:back-matter
Generate acknowledgments, about the author, reading group guide, also by, and more.
Description: Generate marketing blurb in three variations for back cover and retailer listings.
Usage: /scr:blurb
Prerequisites: Complete draft must exist
Available for: Prose, script, visual, poetry, interactive, sacred
Example:
/scr:blurb
Get three blurb variations: punchy (Amazon listing), standard (back cover), extended (Goodreads).
Description: Generate plot synopsis at specified length for query and submission packages.
Usage: /scr:synopsis
Prerequisites: Complete draft must exist
Available for: Prose, script, visual
Example:
/scr:synopsis
Generate a 1-page and 3-page synopsis for agent submissions.
Description: Generate agent query letter adapted to genre conventions.
Usage: /scr:query-letter
Prerequisites: Blurb and synopsis must exist
Available for: Prose, script, sacred
Example:
/scr:query-letter
Draft a query letter following genre conventions with hook, pitch, bio, and comp titles.
Description: Generate nonfiction book proposal for agent or publisher submission.
Usage: /scr:book-proposal
Prerequisites: Synopsis must exist
Available for: Prose, sacred (nonfiction only)
Example:
/scr:book-proposal
Generate a full book proposal: overview, market analysis, chapter summaries, author platform, sample chapter.
Description: Generate reading group discussion questions exploring themes, characters, and craft.
Usage: /scr:discussion-questions
Prerequisites: Complete draft must exist
Available for: Prose
Example:
/scr:discussion-questions
Generate 10-15 book club questions that spark real conversation about your themes.
Description: Publishing wizard or preset-driven pipeline. Chains export commands based on destination.
Usage: /scr:publish [--preset <preset>] [--all] [--skip-validate]
Prerequisites: None (wraps export commands)
Flags:
--preset <preset>-- Use a preset such askdp-paperback,kdp-ebook,ebook-wide,ingram-paperback,query-submission, orscreenplay-query--all-- Run all applicable presets--skip-validate-- Skip the scaffold-marker validation gate (not recommended)
Available for: All work types
Example:
/scr:publish --preset kdp-paperback
Run the full KDP paperback publishing pipeline: prepare the interior package, generate the platform handoff brief, and use the finished print cover from .manuscript/build/paperback-cover.pdf.
Description: Compile and export manuscript to publication-ready formats.
Usage: /scr:export --format <format> [--formatted] [--print-ready] [--skip-validate]
Prerequisites: Complete draft must exist
Flags:
-
--format-- Target format: markdown, docx, pdf, epub, fountain, fdx, latex, kdp-package, ingram-package, submission-package, query-package -
--formatted-- Use designed/formatted template (vs. manuscript format) -
--print-ready-- Generate the interior print PDF surface used by print-package flows -
--skip-validate-- Skip the scaffold-marker validation gate (not recommended) Available for: All work types (format availability varies by work type)
Example:
/scr:export --format epub
Export your manuscript as a publication-ready EPUB with proper metadata, table of contents, and styling.
Description: Build EPUB with platform-aware accessibility guardrails (Pandoc + EAA compliance).
Usage: /scr:build-ebook [--platform <platform>] [--fixed-layout] [--skip-validate]
Prerequisites: Complete draft must exist
Flags:
--platform <platform>-- Target retailer: kdp, ingram, apple, bn, d2d, kobo, google, smashwords--fixed-layout-- Produce fixed-layout EPUB output for picture books and illustrated books--skip-validate-- Skip scaffold-marker validation (not recommended)
Available for: Prose, visual, poetry, interactive, sacred
Example:
/scr:build-ebook --platform kdp
Build a retailer-ready EPUB with metadata, accessibility checks, and platform-aware styling.
Description: Build print-ready PDF with trim-size guardrails, or academic .tex output for publisher wrapper platforms. Pair the interior with .manuscript/build/paperback-cover.pdf or .manuscript/build/hardcover-cover.pdf rather than relying on hard-coded wrap geometry.
Usage: /scr:build-print [--platform <platform>] [--trim <size>] [--strict] [--hardcover] [--skip-validate]
Prerequisites: Complete draft must exist
Flags:
--platform <platform>-- Target print or academic platform: kdp, ingram, ieee, acm, lncs, elsevier, apa7--trim <size>-- Trim size for print-book output: 5x8, 5.25x8, 5.5x8.5, 6x9, 7x10--strict-- Turn page-count warnings into hard failures--hardcover-- Apply hardcover page limit for KDP--skip-validate-- Skip scaffold-marker validation (not recommended)
Available for: Prose, script, visual, poetry, sacred, academic
Example:
/scr:build-print --platform kdp --trim 6x9
Build a print-ready PDF with platform guardrails, or use an academic platform to emit .tex source instead.
Description: Build Smashwords/D2D-compliant DOCX via Pandoc reference doc.
Usage: /scr:build-smashwords [--skip-validate]
Prerequisites: Complete draft must exist
Flags:
--skip-validate-- Skip scaffold-marker validation (not recommended)
Available for: Prose, visual
Example:
/scr:build-smashwords
Build a distribution-ready DOCX using the Smashwords/D2D reference document and formatting rules.
Description: Build poetry submission manuscript DOCX with one poem per page, title page, and conditional TOC.
Usage: /scr:build-poetry-submission [--skip-validate]
Prerequisites: Complete draft must exist
Flags:
--skip-validate-- Skip scaffold-marker validation (not recommended)
Available for: Poetry
Example:
/scr:build-poetry-submission
Build a poetry-submission DOCX for journal or contest submission using the poetry reference document.
Description: Run full publishing pipeline unattended with quality gate (voice-check + continuity-check).
Usage: /scr:autopilot-publish --preset <preset>
Prerequisites: Complete draft must exist
Flags:
--preset <preset>-- Publishing preset to run
Available for: All work types
Example:
/scr:autopilot-publish --preset kdp
Run quality checks and then generate all KDP deliverables automatically.
Commands for generating cover art, scene illustrations, character references, maps, and visual layouts.
Description: Generate structured cover art prompts and delivery briefs for ebook, paperback, and hardcover cover assets.
Usage: /scr:cover-art [--trim <size>] [--kdp <trim_size>] [--series] [--prompt-only] [--element front|spine|back|full-wrap]
Prerequisites: WORK.md must exist
Available for: Prose, visual, poetry, sacred
Flags:
--trim <size>-- Preferred trim shorthand for prompt framing--kdp <trim_size>-- Legacy alias for--trim--series-- Generate series-consistent cover--prompt-only-- Generate prompts without calling image API--element-- Generate specific cover element
Example:
/scr:cover-art --trim 6x9 --element front
Generate a front-cover prompt and delivery brief while keeping the final packaged files under .manuscript/build/.
Description: Generate a scene-specific illustration prompt with character visuals, setting, and mood.
Usage: /scr:illustrate-scene <scene-ref> [--style <style>]
Prerequisites: ART-DIRECTION.md and draft must exist
Available for: Prose, visual, interactive, sacred
Flags:
--style <style>-- Art style override
Example:
/scr:illustrate-scene 3-2 --style watercolor
Generate an illustration prompt for Chapter 3, Scene 2 in watercolor style.
Description: Generate a character visual reference sheet prompt for illustration consistency.
Usage: /scr:character-ref <name> [--style <style>]
Prerequisites: CHARACTERS.md must exist
Available for: Prose, script, visual, interactive
Flags:
--style <style>-- Art style for the reference sheet
Example:
/scr:character-ref Maria --style "realistic pencil"
Generate a character reference sheet for Maria to keep illustrations consistent.
Description: Generate or refine the visual style bible for illustrations and cover art.
Usage: /scr:art-direction [--refine]
Prerequisites: None
Available for: Prose, visual, interactive, sacred
Flags:
--refine-- Refine existing art direction
Example:
/scr:art-direction
Create ART-DIRECTION.md with color palette, style references, mood, and visual motifs for your book.
Description: Generate decorative chapter header/ornament design prompts.
Usage: /scr:chapter-header [--style <style>] [--chapter <ref>]
Prerequisites: None
Available for: Prose, sacred
Flags:
--style <style>-- Ornament style--chapter <ref>-- Specific chapter
Example:
/scr:chapter-header --style "art nouveau floral"
Generate decorative header designs for each chapter in art nouveau style.
Description: Generate world or regional map illustration prompts from WORLD.md geographic content.
Usage: /scr:map-illustration [--region <area>] [--style <style>]
Prerequisites: WORLD.md must exist
Available for: Prose, visual, interactive, sacred
Flags:
--region <area>-- Focus on a specific region--style <style>-- Map style (fantasy, antique, satellite, etc.)
Example:
/scr:map-illustration --style "tolkien-style hand-drawn"
Generate a fantasy map prompt based on the geography in your world-building document.
Description: Generate children's book page spread layouts with text and illustration zones.
Usage: /scr:spread-layout <spread-number> [--text-ratio <percent>]
Prerequisites: None
Available for: Visual (children's books, picture books)
Flags:
--text-ratio <percent>-- Percentage of spread dedicated to text
Example:
/scr:spread-layout 4 --text-ratio 30
Design spread 4 with 30% text and 70% illustration area.
Description: Generate comic panel layouts with composition notes and balloon placement.
Usage: /scr:panel-layout <page-number> [--panels <count>] [--style <style>]
Prerequisites: None
Available for: Visual (comics only)
Flags:
--panels <count>-- Number of panels on the page--style <style>-- Layout style
Example:
/scr:panel-layout 12 --panels 6
Design a 6-panel layout for page 12 with composition and balloon placement notes.
Description: Generate storyboard frames for script and visual work types with camera direction.
Usage: /scr:storyboard [--scene <ref>] [--act <number>]
Prerequisites: None
Available for: Script, visual
Flags:
--scene <ref>-- Storyboard a specific scene--act <number>-- Storyboard an entire act
Example:
/scr:storyboard --scene 2-3
Generate storyboard frames for Act 2, Scene 3 with camera angles, movement, and blocking notes.
Commands for translating your manuscript into other languages with consistency and cultural awareness.
Description: Translate manuscript to target language with glossary and translation memory support. Uses fresh-context-per-unit pattern for consistency.
Usage: /scr:translate <language> [--all] [--from <unit>] [--languages] [--add-language <lang>]
Prerequisites: Complete draft must exist
Flags:
--all-- Translate all units--from <unit>-- Start from a specific unit--languages-- List configured target languages--add-language <lang>-- Add a new target language
Available for: All work types
Example:
/scr:translate french --all
Translate the entire manuscript to French, unit by unit, using your glossary and translation memory.
Description: Create and manage bilingual term glossary for consistent translation.
Usage: /scr:translation-glossary <language> [--add <term> --translation <value>] [--import] [--review] [--category <cat>]
Prerequisites: None
Flags:
--add <term> --translation <value>-- Add a term--import-- Import terms from existing translations--review-- Review glossary entries--category <cat>-- Filter by category
Available for: All work types
Example:
/scr:translation-glossary spanish --add "the Fold" --translation "el Pliegue"
Ensure "the Fold" is always translated as "el Pliegue" throughout the Spanish edition.
Description: Build and manage translation memory from completed translations.
Usage: /scr:translation-memory <language> [--build] [--stats] [--export] [--clear]
Prerequisites: Translation must exist for the language
Flags:
--build-- Build memory from existing translations--stats-- Show translation memory statistics--export-- Export memory for reuse--clear-- Clear translation memory
Available for: All work types
Example:
/scr:translation-memory french --build
Build translation memory from your completed French translation for reuse in future projects.
Description: Flag idioms, humor, customs, and cultural references that need localization for target language.
Usage: /scr:cultural-adaptation <language> [--unit <unit>] [--severity <level>] [--report]
Prerequisites: Translation must exist for the language
Flags:
--unit <unit>-- Check a specific unit--severity <level>-- Filter by severity--report-- Generate a full report
Available for: All work types
Example:
/scr:cultural-adaptation japanese --report
Generate a report of cultural references that need adaptation for Japanese readers.
Description: Translate the translation back to source language and show side-by-side comparison with drift annotations.
Usage: /scr:back-translate <language> [--unit <unit>] [--report]
Prerequisites: Translation must exist for the language
Flags:
--unit <unit>-- Check a specific unit--report-- Generate a comparison report
Available for: All work types
Example:
/scr:back-translate french --report
Verify your French translation by translating it back to English and comparing with the original.
Description: Export translated editions in all target formats with localized front/back matter and language-specific formatting.
Usage: /scr:multi-publish [--languages <lang1,lang2,...>] [--format <format>] [--all-languages] [--all-formats]
Prerequisites: Translation must exist
Flags:
--languages-- Specific languages to publish--format-- Target format--all-languages-- Publish all translated languages--all-formats-- Export in all available formats
Available for: All work types
Example:
/scr:multi-publish --all-languages --format epub
Generate EPUBs for every translated edition with localized front/back matter.
Description: Run multi-language translation pipeline unattended with glossary, translation, adaptation, and publishing.
Usage: /scr:autopilot-translate [--languages <lang1,lang2,...>] [--all-languages] [--skip-publish] [--skip-adaptation] [--resume]
Prerequisites: Complete draft must exist
Flags:
--languages-- Target languages--all-languages-- Translate to all configured languages--skip-publish-- Skip the publishing step--skip-adaptation-- Skip cultural adaptation--resume-- Resume interrupted pipeline
Available for: All work types
Example:
/scr:autopilot-translate --languages french,spanish,german
Translate to French, Spanish, and German end-to-end: glossary, translation, cultural adaptation, and publishing.
Commands for managing revision tracks and collaborative workflows.
Description: Manage revision tracks -- create, switch, compare, merge, and propose changes for review.
Usage: /scr:track <create|list|switch|compare|merge|propose> [name] [options]
Prerequisites: None
Subcommands:
create-- Create a new revision tracklist-- List all tracksswitch-- Switch to a different trackcompare-- Compare a revision track against canon or another trackmerge-- Merge a track into the canon manuscriptpropose-- Propose changes from a track for review
Available for: All work types
Example:
/scr:track create "experimental-ending"
Create a revision track to experiment with an alternate ending without affecting your canon manuscript.
General-purpose commands for project management, quick edits, notes, and system health.
Description: Interactive command center for managing multiple writing projects.
Usage: /scr:manager [--list] [--switch <project>] [--status]
Prerequisites: None
Flags:
--list-- List all projects--switch <project>-- Switch to a different project--status-- Show status of all projects
Available for: All work types
Example:
/scr:manager --list
See all your writing projects with status, word count, and last activity.
Description: Diagnose and repair common project state issues.
Usage: /scr:health [--repair]
Prerequisites: None
Flags:
--repair-- Attempt to fix detected issues
Available for: All work types
Example:
/scr:health --repair
Check for missing files, broken references, and state inconsistencies, then fix what can be fixed.
Description: Strip template scaffold markers from draft files. Dry-run by default.
Usage: /scr:cleanup [--apply]
Prerequisites: Draft files must exist
Flags:
--apply-- Modify files in place instead of showing a dry-run preview
Available for: All work types
Example:
/scr:cleanup --apply
Remove scaffold markers, Alternate blocks, and duplicate H1 headings from the draft files in place.
Description: Scan manuscript for unresolved scaffold markers before export.
Usage: /scr:validate
Prerequisites: Draft files must exist
Available for: All work types
Example:
/scr:validate
Check whether the manuscript is clean enough to export, and list every blocking scaffold marker if it is not.
Description: Make a quick inline edit without full planning overhead. For small fixes and tweaks.
Usage: /scr:fast <description of edit>
Prerequisites: None
Available for: All work types
Example:
/scr:fast "change Maria's hair from brown to black in chapter 3"
Make a targeted edit without going through the full plan-draft-review cycle.
Description: Add a quick note or reminder to the project notes file.
Usage: /scr:add-note <note text>
Prerequisites: None
Available for: All work types
Example:
/scr:add-note "Research 1920s speakeasy slang for chapter 7"
Jot down a thought for later without losing your flow.
Description: Review all project notes.
Usage: /scr:check-notes [--clear]
Prerequisites: None
Flags:
--clear-- Clear all notes after review
Available for: All work types
Example:
/scr:check-notes
Review everything you've jotted down during your writing sessions.
Description: Plant a creative seed -- an idea, image, or fragment for future use.
Usage: /scr:plant-seed <idea>
Prerequisites: None
Available for: All work types
Example:
/scr:plant-seed "What if the detective's daughter is the real thief?"
Save a story idea for later without committing to it now.
Description: Diagnose why something isn't working and suggest fixes.
Usage: /scr:troubleshoot [description of problem]
Prerequisites: None
Available for: All work types
Example:
/scr:troubleshoot "draft command says OUTLINE.md is missing but it exists"
Scriven investigates the issue and tells you exactly what's wrong and how to fix it.
Description: Start or continue a focused conversation thread on a specific topic.
Usage: /scr:thread <topic name>
Prerequisites: None
Available for: All work types
Example:
/scr:thread "magic system rules"
Start a dedicated conversation about your magic system that you can return to anytime.
Description: View or modify project settings.
Usage: /scr:settings
Prerequisites: None
Available for: All work types
Example:
/scr:settings
Review and adjust your project configuration -- work type, autopilot profile, developer mode, voice drift threshold, and the draft block (drafter quality controls).
Drafter quality knobs (1.6.0+):
draft.rigor:standardorstrict. Strict prepends a per-sentence rules check, useful when routing to weaker models.draft.context_profile:minimal,standard, orfull. Controls how much context the drafter loads per atomic unit.minimalsaves tokens;fullloads cross-document references for sacred-work continuity.draft.pitfalls_enabled:trueorfalse. Whenfalse, skip loading the per-work-type pitfall pack fromtemplates/pitfalls/<work_type>.md. WRITING-RULES.md still loads.
See Drafter Quality for the full system and model-tier recommendations.
Description: Build or refine the writer's Voice DNA profile through questionnaire, sample analysis, or reference authors.
Usage: /scr:profile-writer [--questionnaire] [--analyze <file>] [--reference] [--all] [--refine] [--refresh] [--export] [--import]
Prerequisites: None
Flags:
--questionnaire-- Build profile through questions--analyze <file>-- Analyze a writing sample--reference-- Build from reference authors--all-- Run all three methods--refine-- Refine existing profile--refresh-- Rebuild from scratch--export-- Export voice profile--import-- Import voice profile
Available for: All work types
Example:
/scr:profile-writer --analyze ~/Documents/my-essay.md
Build your Voice DNA profile by analyzing an existing piece of your writing.
Commands available only for sacred and historical work types (scripture, commentary, devotional, liturgical, historical chronicle, religious epic, sermon, etc.). These commands are hidden from other work types.
Description: Show verse numbering format for the active sacred tradition.
Usage: /scr:sacred-verse-numbering [--example <text>]
Prerequisites: .manuscript/config.json must include a valid tradition
Flags:
--example <text>-- Format an example citation using the active tradition's numbering style
Example:
/scr:sacred-verse-numbering --example "John 3 16"
Show the active tradition's numbering format and render an example citation using that system.
Description: Build or search a concordance of key terms, names, and phrases across the sacred text. Essential for cross-referencing and intertextual study.
Usage: /scr:sacred:concordance [--build] [--search <term>] [--tradition <tradition>]
Prerequisites: Draft must exist
Flags:
--build-- Build the concordance from the text--search <term>-- Search for a specific term--tradition <tradition>-- Filter by tradition
Example:
/scr:sacred:concordance --search "covenant"
Find every occurrence of "covenant" across the text with surrounding context and cross-references.
Description: Map connections between passages -- parallel accounts, prophetic fulfillments, intertextual echoes, typological links.
Usage: /scr:sacred:cross-reference [--passage <ref>] [--type <parallel|fulfillment|echo|typology>]
Prerequisites: Draft must exist
Flags:
--passage <ref>-- Start from a specific passage--type-- Filter by reference type: parallel, fulfillment, echo, typology
Example:
/scr:sacred:cross-reference --passage "Genesis 22" --type typology
Find typological connections to the binding of Isaac across the text.
Description: Build and verify genealogical trees and lineages for figures in the text. Catches contradictions across chapters.
Usage: /scr:sacred:genealogy [--verify] [--figure <name>] [--tradition <tradition>]
Prerequisites: FIGURES.md must exist with at least 2 figures
Flags:
--verify-- Check for genealogical contradictions--figure <name>-- Focus on a specific figure--tradition <tradition>-- Use tradition-specific lineage data
Example:
/scr:sacred:genealogy --figure Abraham --verify
Build Abraham's genealogical tree and verify consistency across all mentions in the text.
Description: Timeline management with era-appropriate dating systems. Handles overlapping calendars and disputed dates.
Usage: /scr:sacred:chronology [--calendar <system>] [--verify] [--range <start>-<end>]
Prerequisites: None
Flags:
--calendar <system>-- Calendar system: gregorian, hebrew, hijri, vikram_samvat, buddhist_era, regnal--verify-- Check for chronological contradictions--range-- Focus on a specific date range
Example:
/scr:sacred:chronology --calendar hebrew --verify
Build a timeline using the Hebrew calendar and verify dates are consistent across the text.
Description: Add or manage a commentary/exegetical layer alongside the primary sacred text. Support multiple annotation traditions simultaneously.
Usage: /scr:sacred:annotation-layer [tradition_name] [--list] [--remove <tradition>]
Prerequisites: Draft must exist
Flags:
--list-- List all annotation layers--remove <tradition>-- Remove an annotation layer
Example:
/scr:sacred:annotation-layer reformed
Add a Reformed theological annotation layer to your text alongside existing Catholic annotations.
Description: Manage verse/ayah/pasuk numbering systems. Handles differences between traditions (Masoretic vs. Septuagint numbering, Hafs vs. Warsh Quranic numbering, etc.).
Usage: /scr:sacred:verse-numbering [--system <system>] [--convert <from>-<to>] [--verify]
Prerequisites: Draft must exist
Flags:
--system <system>-- Numbering system: masoretic, septuagint, quranic_hafs, quranic_warsh, pali_canon--convert <from>-<to>-- Convert between numbering systems--verify-- Verify numbering consistency
Example:
/scr:sacred:verse-numbering --convert masoretic-septuagint
Show how verse numbers differ between Masoretic and Septuagint traditions.
Description: Track primary sources, oral traditions, manuscript variants, and source attributions. For historical and critical editions.
Usage: /scr:sacred:source-tracking [--add <source>] [--list] [--verify]
Prerequisites: WORK.md must exist
Flags:
--add <source>-- Add a primary source--list-- List all tracked sources--verify-- Verify source attributions
Example:
/scr:sacred:source-tracking --add "Dead Sea Scrolls, 1QIsaA"
Track the Dead Sea Scrolls as a primary source for your critical edition.
Description: Verify internal theological and doctrinal consistency across the text. Flag contradictions in doctrine, moral teaching, or cosmological claims.
Usage: /scr:sacred:doctrinal-check [unit number]
Prerequisites: Draft and DOCTRINES.md must exist
Example:
/scr:sacred:doctrinal-check
Scan the entire text for doctrinal inconsistencies -- contradictions in theology, moral teaching, or cosmology.
Many commands automatically rename based on your work type group. Here is a summary:
| Base Command | Academic Label | Sacred Label |
|---|---|---|
/scr:editor-review |
peer-review |
scholarly-review |
/scr:beta-reader |
reviewer-simulation |
theological-review |
/scr:voice-check |
-- | register-check |
/scr:sensitivity-review |
ethics-review |
interfaith-review |
Sacred-specific flow labels like chronology and doctrinal-check are exposed through the dedicated /scr:sacred:* command family rather than by relabeling hidden base commands.
Commands with adaptive terminology (discuss, plan, draft, submit) keep the runnable command id stable and change only the unit wording in prompts and output. For example, a novel still runs /scr:draft 5, but Scriven frames it as drafting Chapter 5. A screenplay frames the same command as drafting Act 5. A Quranic commentary frames it as drafting Surah 5.
This reference is maintained against data/CONSTRAINTS.json and the live command tree in commands/scr/. For the most current project-scoped menu, run /scr:help inside your project.