document-writing-orchestratorlisted

# Document Writing Orchestrator Produce a document that performs its intended job, stays faithful to its evidence, and remains coherent as it evolves. Scale the process to the assignment instead of imposing orchestration on every edit. ## Choose the lightest effective workflow Handle a short, self-contained draft or narrow copyedit directly. Use an orchestrated workflow when the document is substantial, its sections depend on one another, source provenance matters, the document has meaningful real-world consequences, or an independent review would materially improve confidence. For orchestrated work, read [references/agent-prompts.md](references/agent-prompts.md) in full before spawning agents. Keep this skill and its reference in the orchestrator. Give each agent a fresh, role-specific prompt containing only the context its role needs. Use the strongest role isolation the runtime offers: separate agents, tasks, or context windows. If none is available, run explicit sequential role passes with separate context packets and disclose at handoff that the review was not independently isolated. Do not pretend a same-context review is independent. Choose the editing unit deliberately: - Work on the whole document when the argument, voice, or cross-references dominate and the file fits comfortably in context. - Work section by section when the document is long, later draft prose could bias the current section, or an explicit dependency order matters. Finish with a whole-do