doc-coauthoring

Structured document collaboration uses context collection, iterative part-by-part drafting, and a final no-context reader test to coauthor PRDs and RFCs, validating reader effectiveness. It guides brainstorming, gap checks, and precise editing to ensure shared understanding.

Reader effectiveness testing validates technical specifications and decision docs by testing the final document with a fresh model that has no prior context. It surfaces ambiguities and missing assumptions to detect gaps that hinder accurate communication.

Collaborative proposal writing starts with context-first alignment, collecting document type, audience, goals, constraints, and relevant background. This closes the gap between author knowledge and reader needs before iterative drafting begins.

Iterative drafting builds design documents part-by-part through targeted clarification questions, brainstorm options, keep/delete/merge planning, gap checks, and precise editing. This structured approach ensures each section meets audience and goal requirements.

Structured document collaboration is needed for technical specifications when accurate communication and shared understanding matter. It applies to creating PRDs, RFCs, proposals, and decision docs where reader gaps and ambiguities must be detected and resolved.

Document collaboration guides proposal writing without predefined templates by orchestrating a three-phase process: context collection, iterative structured drafting, and reader effectiveness testing. It builds structure dynamically based on audience, goals, and constraints.