doc-coauthoring

Guide collaborative document creation through context gathering, refinement, and reader testing.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/lDuang/mcp-skill-registry --skill doc-coauthoring-lduang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/lDuang/mcp-skill-registry/tree/main/skill/doc-coauthoring
Command: npx skills add https://github.com/lDuang/mcp-skill-registry --skill doc-coauthoring-lduang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides users through a structured, stage-based approach to creating high-quality documents, proposals, technical specs, and decision records, ensuring clarity, traceability, and reader readiness.

Core Features & Use Cases

  • Three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing to coordinate collaboration.
  • Iterative drafting & validation: Build sections with clarifying questions, brainstorm options, and surgical edits to converge on a strong document.
  • Use Case: Teams creating technical specs or design proposals can use this workflow to capture context, iterate efficiently, and validate the document with a fresh reader.

Quick Start

Provide your document context to begin Stage 1 of the structured co-authoring workflow.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
What is a structured co-authoring workflow for technical documentation?

A structured co-authoring workflow guides teams through Context Gathering, Refinement & Structure, and Reader Testing to create technical specs and proposals. It ensures document clarity, traceability, and reader readiness by using iterative feedback loops and validation.

How do I coordinate collaborative writing for technical specs and proposals?

You coordinate collaborative writing by progressing through three stages: capturing context, refining structure with surgical edits, and validating the document with a fresh reader. This stage-based approach aligns stakeholders and converges on a strong final draft.

Can I use this workflow for decision records and design proposals?

Yes, this workflow applies to writing decision records, design proposals, technical specs, and other structured content. It captures context and iterates efficiently to validate the document with readers before finalization.

What is the best way to validate technical documentation with stakeholders?

The best way to validate technical documentation is through a dedicated Reader Testing stage. This stage uses iterative feedback loops and a fresh reader perspective to ensure the document is clear, traceable, and reader-ready.

How do I start the document co-authoring process?

To start the document co-authoring process, provide your document context to begin Stage 1. The workflow then guides you through brainstorming options, making surgical edits, and validating sections with stakeholders.

Why use a stage-based approach for collaborative document creation?

Using a stage-based approach for collaborative document creation solves the problem of unstructured drafting by separating context gathering, refinement, and reader testing. This ensures high-quality, traceable documents without missing critical stakeholder requirements.