doc-coauthoring

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

4|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/MagicBowen/dogent --skill doc-coauthoring-magicbowen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/MagicBowen/dogent/tree/main/claude/skills/skills/doc-coauthoring
Command: npx skills add https://github.com/MagicBowen/dogent --skill doc-coauthoring-magicbowen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Co-authoring documentation often suffers from fragmented context, unclear structure, and misaligned stakeholder expectations. This workflow provides a guided, staged process to capture context, iteratively refine content, and validate readability before publishing.

Core Features & Use Cases

  • Context Gathering: Collect background, audience, objectives, and constraints through guided prompts to reduce back-and-forth.
  • Refinement & Structure: Breaks the doc into sections, proposes options, and iterates with surgical edits to improve clarity and coherence.
  • Reader Testing: Runs a fresh review pass to surface ambiguities and gaps, ensuring the document works for readers who lack prior context.
  • Artifact-backed Drafting: Creates a living scaffold (sections and placeholders) to organize work and track progress.
  • Adaptability: Useful for writing documentation, proposals, technical specs, decision documents, or any structured content.

Quick Start

Initiate the co-authoring workflow for a new document by starting Stage 1: Context Gathering and answering the initial questions.

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 and proposals with a structured workflow?▼

Structured co-authoring for technical specs and proposals uses a staged workflow with context gathering, iterative refinement, and reader testing to ensure clarity, reviewability, and reader-friendliness across teams.

What is the best way to write documentation that ensures readability for stakeholders lacking prior context?▼

The best way to write documentation for context-lacking stakeholders is running a fresh reader testing pass after drafting, which surfaces ambiguities and gaps to validate the document works for its intended audience.

How do I start drafting a decision record using a guided co-authoring process?▼

Start drafting a decision record by initiating Stage 1: Context Gathering, answering guided prompts about background, audience, objectives, and constraints to reduce back-and-forth before generating the artifact-backed draft.

Can I use this structured content writing workflow for team collaboration on technical documents?▼

Yes, you can use this structured content writing workflow for team collaboration on technical documents, proposals, and decision records, providing staged handoffs and artifact-based drafting to align stakeholder expectations.

How does artifact-backed drafting improve the documentation review process?▼

Artifact-backed drafting improves the documentation review process by creating a living scaffold with sections and placeholders, organizing work and tracking progress to enable surgical edits and coherent iterative refinement.