doc-coauthoring

Co-authoring technical specifications involves iterative context gathering, section-by-section brainstorming, and drafting to build structured RFCs. The workflow refines document scaffolds and performs surgical edits to ensure the final artifact accurately captures project trade-offs.

Context gathering for decision documents requires collecting background, constraints, stakeholders, and timelines before reasoning about trade-offs. This process builds a document scaffold, brainstorming section contents and curating priorities to ensure accurate technical decisions.

Reader testing for design docs simulates a fresh reader via sub-agents or manual instructions. This surfaces ambiguities, assumptions, and missing information before publishing, ensuring the technical specifications are clear for cross-functional reviewers.

The co-authoring workflow supports drafting PRDs, proposals, and design docs during both solo and collaborative authoring sessions. It iteratively refines document sections and applies surgical edits to finalize the artifact.

To start document drafting without a template, describe the document type and audience, or paste existing project context. The workflow collects the necessary background and constraints to build a scaffold and begin section-by-section drafting.

Reader testing for RFCs via sub-agents is an optional step that simulates fresh readers to catch ambiguities. If not explicitly triggered, reader testing requires manual instructions to surface missing information and assumptions before publishing.