doc-coauthoring

Co-authoring technical documentation is done through a structured three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This process guides teams with clarifying questions and iterative edits to reduce ambiguity and rework.

Drafting RFCs and decision records collaboratively requires a guided workflow that handles context gathering, structural refinement, and reader testing. This approach drives section scaffolding and iterative edits to ensure clarity without needing external tools.

Writing proposals without external dependencies is supported by encoding the co-authoring workflow directly into prompts. The skill handles brainstorming options and structural edits entirely on its own without requiring external tools or integrations.

Collaborative document creation handles context gathering and structure refinement through interactive guidance. It drives clarifying questions and section scaffolding, allowing you to indicate changes and learn preferences for iterative edits across future sections.

You do not need to accept the structured workflow to start drafting technical specs. If the structured co-authoring workflow is declined, you can switch to freeform drafting and proceed with your document independently.

You should not use a guided co-authoring workflow when your document requires direct editing rather than section-by-section indication of changes. The workflow encodes steps that drive questions and iterative edits instead of applying modifications directly to the text.