doc-coauthoring

Guides users through structured, iterative co-authoring workflows for collaborative documents.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill doc-coauthoring-kmshihab7878
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/doc-coauthoring
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill doc-coauthoring-kmshihab7878

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many collaborative documents fail because authors and reviewers do not share the same context, leading to unclear proposals, missing assumptions, and time-consuming revision cycles. This workflow closes the context gap, structures iterative drafting, and validates the doc from a fresh-reader perspective so the final document actually works for its audience.

Core Features & Use Cases

  • Three-stage guided workflow: Context Gathering, Refinement & Structure, and Reader Testing to move from raw context to a production-ready document.
  • Iterative section-by-section drafting: Clarifying questions, brainstorming, curation, drafting, and surgical edits with artifact operations (create_file, str_replace) to learn author preferences.
  • Reader validation and connector integration: Predict reader questions, run fresh-instance tests via sub-agents when available, and check for ambiguities, missing assumptions, and accessibility issues (e.g., images without alt-text).
  • Use Case: Producing a technical specification or decision document with multiple stakeholders and linked artifacts, where context transfer and reader validation are critical.

Quick Start

Use the doc-coauthoring workflow to draft a decision document by dumping context, choosing a section structure, and iteratively refining each section until reader testing passes.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I write technical specs with multiple stakeholders to ensure reader clarity?

Writing technical specs with multiple stakeholders requires structured co-authoring workflows that transfer context, iteratively refine section content, and validate the document from a fresh-reader perspective to ensure reader clarity.

What is the best way to draft a collaborative PRD or RFC without missing assumptions?

The best way to draft a collaborative PRD or RFC without missing assumptions is using a three-stage workflow: gathering context, iteratively refining structure, and running reader validation to check for ambiguities.

How do I iteratively edit technical proposals section by section?

You iteratively edit technical proposals section by section by applying artifact operations like str_replace to draft, curate, and make surgical edits, guided by clarifying questions that learn author preferences.

Can I run automated reader testing on decision documents to predict reader questions?

Yes, you can run automated reader testing on decision documents by using sub-agents to validate as fresh instances, predicting reader questions, checking for missing assumptions, and ensuring accessibility compliance.

What is the best way to structure a collaborative writing workflow for proposal documents?

The best way to structure a collaborative writing workflow for proposal documents is moving sequentially through context gathering, refinement and structure drafting, and final reader testing to achieve production-ready output.

Does collaborative document drafting work without prior context transfer between authors and reviewers?

Collaborative document drafting fails without context transfer because authors and reviewers lacking shared context produce unclear proposals and enter time-consuming revision cycles instead of generating reader-ready documents.