doc-coauthoring

Guide teams through three-stage documentation workflows for technical specs and design documents.

10|2|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Yrzhe/telegram-claude-bot --skill doc-coauthoring-yrzhe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/Yrzhe/telegram-claude-bot/tree/main/.claude/skills/doc-coauthoring
Command: npx skills add https://github.com/Yrzhe/telegram-claude-bot --skill doc-coauthoring-yrzhe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Co-authoring structured, reader-tested documentation is time-consuming when done informally. This workflow guides teams through Context Gathering, Refinement & Structure, and Reader Testing to produce clear, usable docs.

Core Features & Use Cases

  • Structured three-stage workflow: Context Gathering, Refinement & Structure, Reader Testing.
  • Guidance on eliciting context, drafting sections, and validating reader comprehension.
  • Use cases include technical specs, proposals, design docs, and decision records.

Quick Start

Begin Stage 1 by sharing the document type, audience, and context to gather, then proceed through Stage 2 and Stage 3 as guided.

Frequently Asked Questions about doc-coauthoring

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

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

A structured documentation co-authoring workflow guides teams through Context Gathering, Refinement & Structure, and Reader Testing to produce clear, reader-tested technical specs, proposals, and design docs.

How do I start co-authoring technical specs with a structured workflow?

Begin co-authoring technical specs by sharing the document type, target audience, and required context to gather, then proceed through iterative refinement and reader validation stages as guided.

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

Yes, you can apply this workflow to design documents and decision records. It supports technical specs, proposals, and similar artifacts by coordinating staged drafting, iterative refinement, and reader validation.

What's the best way to validate reader comprehension for technical proposals?

The best way to validate reader comprehension for technical proposals is through the Reader Testing stage, which enforces reader validation to ensure clarity and reader readiness before finalizing the document.

Does team documentation collaboration require iterative refinement?

Yes, team documentation collaboration requires iterative refinement. The workflow enforces functional requirements for staged drafting and artifact scaffolding to ensure high-quality, usable docs through multiple refinement cycles.