doc-coauthoring

Use a structured co-authoring workflow: first dump all project context and answer clarifying questions, then build the spec section by section through brainstorming and iterative edits, and finally test the draft with a fresh reviewer to catch unclear passages.

Start with context gathering covering audience, goals, and constraints, then agree on a section structure. For each section, review brainstormed options, select what to keep, and refine the draft through targeted feedback until it reads clearly.

Reader testing validates a document by having a fresh reviewer with no prior context answer realistic questions about it. Wrong answers or confusion reveal blind spots, assumed knowledge, and contradictions that the authors can no longer see themselves.

Yes, if integrations or connectors are available, the workflow can pull context directly from messaging channels and shared documents. Without integrations, you paste the relevant content manually into the conversation.

Skip it for short or low-stakes writing where three stages of gathering, refinement, and testing add unnecessary overhead. The workflow is designed for substantial documents like specs, RFCs, and decision docs that many people will read.