write-section

To generate a markdown document chapter, you provide a chapter ID, a doc plan path, and a parts directory, and the system writes a single section that strictly follows the blueprint's required heading hierarchy and formatting rules.

Artifact-grounded content generation ensures all factual content comes only from referenced planning artifacts, inserting placeholders like [待补充：XXX数据] when required data is missing to maintain structural integrity without fabricating information.

The best way to recover a document generation pipeline is by using checkpointing, which writes output parts to a parts directory per chapter so generation can be safely retried after timeouts or partial failures without losing progress.

Yes, you can split document chapter writing into sub-tasks, allowing each chapter to be generated independently with optional sub-task splitting so they can be written separately and later assembled into a complete document.

Yes, blueprint-compliant chapter writing maintains consistent style by reconstructing numbering, citation format, paragraph structure, and terminology preferences from the writer agent or blueprint defaults to ensure a uniform voice across all chapters.

To start writing a document section with checkpoint recovery, you need to provide a chapter_id, a doc_plan_path, and a parts_dir, which are required to enforce numbering, heading hierarchy, and artifact-only factual sourcing.