doc-coauthoring

Guide collaborative document creation through a three-stage co-authoring workflow.

8|3|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/haberlah/dotfiles-claude --skill doc-coauthoring-haberlah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/haberlah/dotfiles-claude/tree/main/skills/doc-coauthoring
Command: npx skills add https://github.com/haberlah/dotfiles-claude --skill doc-coauthoring-haberlah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative documentation often suffers from context gaps, miscommunication, and inconsistent structure. This Skill provides a structured, repeatable workflow to guide teams from initial context to reader-tested docs.

Core Features & Use Cases

  • Three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing, guiding authors from discovery to validation.
  • Iterative drafting with placeholders and targeted refinements to ensure clarity, consistency, and reader readiness.
  • Works across documentation types such as technical specs, proposals, design docs, and decision records.

Quick Start

Offer the three-stage co-authoring workflow and begin at Stage 1: Context Gathering.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I structure collaborative writing for technical proposals?

Structure collaborative writing by guiding your team through a three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This process ensures technical proposals are iteratively drafted with placeholders and validated for reader readiness.

What is the best way to co-author design docs without losing context?

The best way to co-author design docs without losing context is using a structured workflow that begins with Context Gathering. This stage captures initial requirements before moving to iterative drafting and targeted refinements, ensuring consistency across all authors.

Can I use this workflow for decision records and technical specs?

Yes, you can use this workflow for decision records and technical specs. It applies to various documentation types, walking authors through structured stages to ensure clarity, consistency, and reader usability across different document formats.

How do you test documentation for reader usability during creation?

Test documentation for reader usability during creation through the Reader Testing stage. This final phase enforces QA checks on iteratively drafted content to ensure the final document is consistent and ready for readers.

What are the limitations of unstructured document co-authoring?

Unstructured document co-authoring often suffers from context gaps, miscommunication, and inconsistent structure. Without a repeatable workflow guiding stages from discovery to validation, teams struggle to maintain clarity and reader readiness in drafts.