book-writer

You can automate multi-language technical book writing by running a phase-driven workflow that generates overview and supplement documents across ja/ and en/ directories. The process enforces Quarto-ready front matter, cross-references, and callouts while validating links and formatting.

Structuring a technical documentation workflow with cross-references and callouts requires a phase-based approach: preparation, overview drafting, parallel supplement generation, callout enhancement, configuration, and final checks. This maintains consistency across all linked documents.

Yes, you can scaffold both Japanese and English directories for a Quarto book project. The workflow supports ja/ and en/ branches with standardized file naming like 00-overview.qmd and 01-xxx.qmd, alongside structured assets and references directories.

You generate parallel supplement documents for a technical book using sub-agents during Phase 2 of the workflow. These agents create additional context docs and integrate cross-references and callouts directly into the main overview document.

Yes, the Quarto book writing workflow includes formatting and quality checks. It utilizes Phase 5 for final checks, running scripts to fix box drawings, enforce spacing rules, and validate links against established documentation standards.

Your technical documentation needs a phase-driven generation process to prevent excessive manual coordination. It systematically separates drafting, parallel supplement generation, callout enhancement, and final formatting checks to maintain structure and consistency.