Assemble an export-ready manuscript package from the current project state once the manuscript or chapter set is stable enough to be shared, reviewed externally, or archived as a coherent deliverable.
Use this skill to assemble an export package from the accepted project files. It should gather the current manuscript state, remove internal workflow clutter, and produce clean deliverables under 08_exports/ that are ready for external reading, sharing, or archival.
Use this skill when:
Do not use this skill while the project is still too volatile to share coherently unless the goal is an explicit snapshot draft.
Gather or infer these inputs:
story.yaml metadata;Ask questions only when the export scope is genuinely unclear and cannot be inferred safely from the project state.
Always read:
story.yaml05_draft/Read these when present and relevant:
02_story/chapter_list.md02_story/synopsis.md02_story/logline.md06_review/manuscript.review.md06_review/beta_reader_pass.md00_meta/goals.mdreferences/default_html_style.cssDo not include internal review artifacts in the exported manuscript body.
Write or update under 08_exports/:
manuscript_export.mdexport_package.mdexport_manifest.yamldist/style.css when the export will later be turned into HTML and no project-specific stylesheet already existsIf the project already has a clearer export naming pattern, follow it consistently.
manuscript_export.md should contain:
export_package.md should contain:
export_manifest.yaml should contain stable machine-readable metadata, such as:
titlelanguageexported_scopechapter_countproject_statusgenerated_fromnotesIf the export is expected to feed a later HTML build, 08_exports/dist/style.css should provide a sensible default reading stylesheet for the generated HTML. When no project-specific stylesheet is already present and no other stylesheet has been requested, copy the skill resource references/default_html_style.css into 08_exports/dist/style.css.
This skill depends on story.yaml as the source of truth for project metadata.
story.language before writing export content.story.language is missing, gather it before exporting.manuscript_export.md from the selected chapters:
# Title heading in the body, record that downstream HTML generation must avoid emitting a second visible title block.
pandoc, prefer using --metadata pagetitle="..." instead of --metadata title="..." when the body already contains the visible title heading.--metadata title="...", and can additionally use --epub-title-page=false if the workflow wants metadata without a generated title page.export_package.md as a short companion document describing what the export contains.export_manifest.yaml with the core export metadata.08_exports/dist/style.css by copying references/default_html_style.css..html file that can be distributed by sending only that file.The export package should make it easy to answer:
After running the skill, provide:
08_exports/;This skill is done when:
08_exports/ contains a clean manuscript export package;story.language;08_exports/dist/style.css exists when HTML export is expected and no custom stylesheet is already present;references/default_html_style.css when no other stylesheet was specified;Use $prepare-export to assemble the current manuscript into a clean export package for external reading.