doc-coauthoring

Use a structured co-authoring workflow: first dump all project context and answer clarifying questions, then build the doc section by section through brainstorming and curation, and finally test it with a fresh reader to catch blind spots before sharing.

Start with the section containing the most unknowns, usually the core proposal or technical approach. For each section, brainstorm 5-20 candidate points, curate them with the user, draft, and refine through targeted edits rather than rewriting the whole document.

Yes. The Reader Testing stage predicts 5-10 questions real readers would ask, then runs them against a fresh reviewer with no prior context. Incorrect answers or flagged ambiguities are looped back into refinement until the document passes.

Yes. Without sub-agents, the user manually tests the document in a fresh conversation. Without artifacts, sections are drafted into a markdown file in the working directory using placeholder replacement and incremental edits.

Freeform writing suits short or low-stakes documents where reader blind spots carry little risk. The structured workflow is better for substantial docs like RFCs, PRDs, and decision docs where unclear sections affect many readers.