Book Publishing — E-Book Publishing Full Production Pipeline

Workflow

Phase 1: Preparation (Performed Directly by the Orchestrator)

1. Extract from user input:
   • Manuscript: Manuscript file to edit
   • Genre: Business/Self-Help/Fiction/Essay/Technical
   • Publishing Goal: Self-publishing/Publisher submission/Internal distribution
   • Distribution Platforms (optional): Kyobo, Ridibooks, Amazon KDP, etc.
   • Existing Files (optional): Edited manuscript, cover, etc.
2. Create _workspace/ directory and _workspace/covers/ subdirectory
3. Organize the input and save it to _workspace/00_input.md
4. If existing files are present, copy them to _workspace/ and skip the corresponding Phase
5. Determine the execution mode based on the scope of the request

Phase 2: Team Assembly and Execution

Tasks 2a (proofreading) and 2b (cover) are executed in parallel. Both depend on Task 1 (editing).

Inter-team communication flow:

• manuscript-editor complete -> Deliver terminology list to proofreader, tone/genre/target to cover-designer, title/keywords to metadata-manager
• proofreader complete -> Deliver finalized notation to metadata-manager
• cover-designer <-> metadata-manager: Cross-confirm exact title/subtitle/author name notation
• publishing-reviewer cross-validates all deliverables. When RED Must Fix is found, request revisions from the relevant agent -> rework -> re-verify (up to 2 times)

Phase 3: Integration and Final Deliverables

1. Verify all files in _workspace/
2. Confirm that all RED Must Fix items from the review report have been addressed
3. Report the final summary to the user:
   • Edited manuscript — 01_edited_manuscript.md
   • Proofreading report — 02_proofread_report.md
   • Cover concept/images — 03_cover_concept.md
   • Metadata/distribution — 04_metadata.md
   • Review report — 05_review_report.md

Modes by Task Scale

Using Existing Files: When the user provides an edited manuscript, cover, etc., copy the files to the appropriate location in _workspace/ and skip the corresponding agents.

Data Transfer Protocol

File naming convention: {sequence}_{deliverable_name}.{extension}

Error Handling

Test Scenarios

Normal Flow

Prompt: "I want to publish this manuscript as an e-book. It is a self-help book, and I will distribute on Kyobo and Ridibooks." + manuscript file attached Expected Result:

• Editing: Structural + line editing notes, ToC optimization
• Proofreading: Spelling/grammar/notation correction report
• Cover: A/B concept + image generation attempt
• Metadata: BISAC/KDC classification, description, keywords, Kyobo/Ridi distribution settings
• Review: Full consistency matrix, pre-distribution checklist

Existing File Utilization Flow

Prompt: "The manuscript is already edited, just set up the cover and metadata" + edited manuscript attached Expected Result:

• Copy edited manuscript to _workspace/01_edited_manuscript.md
• Cover Mode + Metadata Mode merged: Deploy cover-designer + metadata-manager + reviewer
• Skip manuscript-editor, proofreader

Error Flow

Prompt: "Prepare e-book publishing, no manuscript yet, just have a topic — 'Gen Z Financial Planning'" Expected Result:

• Switch to planning mode: manuscript-editor designs ToC and chapter outlines
• Skip proofreading (no manuscript)
• Cover concept and metadata drafted based on the plan
• Review report notes "Manuscript incomplete, planning stage"

Extended Skills per Agent

Each agent leverages the following extended skills' specialized knowledge to enhance deliverable quality: