Document Synthesis

14.4. Document Synthesis — Synthesizing Documents

From scattered sources into one coherent product

This is the step that connects gathering (14.1, 14.2) with delivering a finished product (14.5): the agent can pull new papers from arXiv, extract the methodology sections, cross-check claims across papers, write synthesis notes — and send you a morning summary of what changed.

Business application — the feedback synthesizer

Feed in support tickets, app store reviews, or sales call notes on a schedule, and get back recurring themes ranked by severity, plus suggested impacts on the roadmap — save this workflow as a skill so the output format stays consistent forever.

Academic application — the research-to-brief pipeline

Hand it a topic on Friday, the agent researches over the weekend, drafts a structured brief, and delivers it on Monday — a clear illustration of how document synthesis combines with cron (chapter 12) and background sessions (chapter 13.4) to run fully unsupervised.

For long-horizon academic writing projects

The dedicated research-paper-writing skill goes further still: tracking state across sessions, scheduling experiment monitoring, counting down deadlines, automatically checking arXiv on a schedule — combining delegation, scheduling, and memory across the entire research lifecycle, not just a single one-off synthesis.

Notes

• For synthesis work that repeats in a fixed format (weekly feedback synthesis, monthly research briefs), save the workflow as a skill from the very first run — guaranteeing a consistent output format across all future runs, following exactly the Reusable Procedures principle described in chapter 10.1.
• For synthesis projects that must run unsupervised over several days (like the weekend research-to-brief pipeline), combine cron + background delegation (chapter 13.4) instead of keeping an interactive session open the whole time.
• When the synthesized content will serve as the basis for real decisions (roadmap, strategy), always pair it with the Sourced Reports step (14.5) — synthesis without clear provenance is easily mistaken for the agent’s opinion rather than grounded synthesis.