doc-coauthoring

Coordinate collaborative documentation creation through a three-stage workflow.

Updated Jul 28, 2025
One-click install
npx skills add https://github.com/hudrazine/claude-code-toolkit --skill doc-coauthoring-hudrazine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/hudrazine/claude-code-toolkit/tree/main/plugins/doc-coauthoring/skills/doc-coauthoring
Command: npx skills add https://github.com/hudrazine/claude-code-toolkit --skill doc-coauthoring-hudrazine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams through a structured, collaborative documentation workflow, reducing back-and-forth, ensuring clarity, and improving reader alignment.

Core Features & Use Cases

  • Context Gathering: collect and align all meta-context before drafting.
  • Refinement & Structure: iteratively build sections through brainstorming, editing, and validation.
  • Reader Testing: verify the document works for readers by testing with a fresh perspective and capturing gaps.
  • Trigger Scenarios: when writing documentation, proposals, specs, or decision documents.
  • On-demand Guidance: acts as an active guide, adapting to document type and audience.

Quick Start

Initiate Stage 1 by telling me the document type and target audience.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I coordinate collaborative documentation across teams without endless back-and-forth?

Collaborative documentation is coordinated through a three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This structured approach aligns team members upfront, iteratively builds document sections, and verifies clarity with a fresh perspective.

What is the best way to structure a technical spec for reader testing?

Reader testing for technical specs is handled by applying an artifact scaffold to structure drafts, followed by testing the document with a fresh perspective to capture gaps. This ensures the final spec works effectively for its intended audience.

Can I use this workflow for writing design docs and decision records?

Yes, the workflow supports writing design docs and decision records. It adapts its on-demand guidance based on the specific document type and target audience you specify when initiating the context gathering stage.

How do we gather context before drafting a proposal?

Context gathering before drafting a proposal is driven by prompting for clarifying questions. The workflow actively collects and aligns all necessary meta-context first, ensuring team alignment before any actual writing begins.

Does this coauthoring workflow enforce a specific process for iterative refinement?

Yes, the coauthoring workflow enforces a strict three-stage process for iterative refinement. It guides teams through brainstorming, editing, and validation steps to systematically build and refine document sections.

When should I not use a structured coauthoring workflow?

A structured coauthoring workflow is not ideal for rapid, informal note-taking or single-author drafts that require no team alignment. It is designed for multi-author documents needing strict context gathering and reader testing.