doc-coauthoring

To co-author technical documentation, this skill organizes collaboration into three structured stages: Context Gathering, Refinement & Structure, and Reader Testing. It uses staged prompts and iterative drafting to ensure reader-ready outputs.

The best way to gather context for proposals or decision docs is starting with Stage 1 of this co-authoring workflow. It collects essential context and clarifying questions upfront to align goals, audience, and success criteria before drafting begins.

Yes, you can iteratively draft and refine a technical spec during Stage 2: Refinement & Structure. This stage helps brainstorm options and converge on a clear document structure through artifact-based collaboration.

Reader testing validates a drafted document by applying a fresh reader perspective during Stage 3. This process surfaces ambiguities, gaps, or assumptions to ensure the final documentation is reader-ready.

Yes, shared artifacts are used to track progress, enable collaboration, and maintain version history. This artifact-driven approach ensures structured co-authoring throughout the documentation workflow.

Yes, this co-authoring workflow applies to writing documentation, proposals, technical specs, and decision docs. It enforces a disciplined process with staged prompts to produce reader-ready outputs across various document types.