doc-coauthoring

Guide staged documentation co-authoring with context gathering, refinement, and reader testing.

3|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/hongbietcode/synthetic-claude --skill doc-coauthoring-hongbietcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/hongbietcode/synthetic-claude/tree/main/plugins/content-creation/skills/doc-coauthoring
Command: npx skills add https://github.com/hongbietcode/synthetic-claude --skill doc-coauthoring-hongbietcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a guided, collaborative workflow for creating well-structured documentation. It helps teams transfer context, iteratively refine content, and ensure readers understand the final document.

Core Features & Use Cases

  • Three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing stages to ensure clarity and completeness.
  • Iterative drafting: Step-by-step section-by-section refinement with explicit feedback loops.
  • Reader-focused validation: Optional Reader Testing with a fresh assistant to catch gaps before publishing.
  • Use case: You need to write a technical spec or proposal with multiple stakeholders; this workflow guides the creation from context gathering to testing.

Quick Start

Start by outlining your document type and audience, then follow Stage 1 (Context Gathering). Use the three-stage process to draft, refine, and validate the document.

Frequently Asked Questions about doc-coauthoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I co-author technical specs with multiple stakeholders?

To co-author technical specs with multiple stakeholders, use a structured three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This process ensures iterative drafting with explicit feedback loops to transfer context and refine content collaboratively.

What is the best way to structure documentation for reader testing?

The best way to structure documentation for reader testing is to apply a staged drafting approach followed by a Reader Testing phase. This uses a fresh assistant to validate clarity and catch gaps, ensuring readers understand the final document before publishing.

How does iterative refinement work for collaborative proposals?

Iterative refinement for collaborative proposals works through step-by-step, section-by-section drafting with explicit feedback loops. This structured workflow allows stakeholders to transfer context and refine content progressively until the document is ready for validation.

Can I use this workflow to write decision documents with multiple stakeholders?

Yes, you can use this workflow to write decision documents with multiple stakeholders. The guided three-stage process applies to specs, proposals, and decision documents, ensuring clarity and completeness from context gathering to final validation.

Do I need any specific tools to run this documentation workflow?

You do not need any specific external tools or dependencies to run this documentation workflow. The process operates independently through Context Gathering, Refinement & Structure, and Reader Testing stages to produce a ready-to-publish document.

When should I not use a structured co-authoring workflow?

You should not use a structured co-authoring workflow for simple, single-author documents that require no stakeholder feedback or reader validation. This process is designed for complex documentation needing iterative refinement, context transfer, and gap catching before publishing.