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 curation, and finally test the draft with a fresh reviewer to catch blind spots.

Start with context gathering about the decision, audience, and constraints. Then iterate on each section by selecting from brainstormed options, drafting, and refining with targeted edits until the document reads clearly.

Reader testing validates a document by having a fresh reviewer with no prior context answer realistic questions about it. It reveals ambiguity, assumed knowledge, and contradictions that authors typically miss.

Yes. Without sub-agents, the user manually tests the doc in a fresh conversation. Without artifacts, sections are drafted in a markdown file in the working directory using the same iterative process.

Skip it for short or informal writing where three stages of iteration add overhead without benefit. The workflow can be declined at the start, and the user can adjust or skip stages at any point.