doc-coauthoring

Guides collaborative document creation through context gathering, iterative drafting, and reader testing.

Updated May 20, 2026
One-click install
npx skills add https://github.com/EZoneLai/claude-plugin-ronsunai-os --skill doc-coauthoring-ezonelai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/EZoneLai/claude-plugin-ronsunai-os/tree/main/commands/doc-coauthoring
Command: npx skills add https://github.com/EZoneLai/claude-plugin-ronsunai-os --skill doc-coauthoring-ezonelai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and specs alone often produces documents that make sense to the author but confuse readers. This Skill structures the co-authoring process so context is fully transferred, each section is refined iteratively, and blind spots are caught before others read the document. ## Core Features & Use Cases - Three-Stage Workflow: Context Gathering (info dumps plus clarifying questions), Refinement & Structure (section-by-section brainstorming, curation, and drafting), and Reader Testing (validating the doc with a fresh, context-free reviewer). - Iterative Section Drafting: For each section, generates clarifying questions, brainstorms 5-20 candidate points, curates with the user, then drafts and refines via targeted edits. - Reader Testing: Predicts questions real readers would ask and tests the document against a fresh Claude instance or sub-agent to surface ambiguity, false assumptions, and contradictions. - Use Case: A product manager drafting a decision doc for a new architecture uses this workflow to dump context, build each section collaboratively, and verify the final doc answers stakeholder questions before circulating it. ## Quick Start Ask the assistant to guide you through co-authoring a decision doc or technical spec using the structured three-stage workflow.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I write a decision doc with AI assistance?

Use a structured co-authoring workflow: first dump all project context and answer clarifying questions, then build the doc section by section through brainstorming and curation, and finally test the draft with a fresh reviewer to catch blind spots before sharing it.

How to structure a technical spec or proposal collaboratively?

Start with the section containing the most unknowns, usually the core proposal or technical approach. For each section, answer clarifying questions, pick from brainstormed options, then refine the draft through targeted edits rather than rewriting the whole document.

Can this workflow test whether my document is clear to readers?

Yes. The Reader Testing stage predicts questions real readers would ask and runs them against a fresh Claude instance or sub-agent with no prior context. Wrong answers or flagged ambiguities reveal gaps to fix before publication.

Does the doc co-authoring workflow work without integrations like Slack or Google Drive?

Yes. Integrations help pull context from channels and shared docs, but without them you can paste content directly into the conversation. The workflow proceeds identically once the context is available.

When should I skip the structured workflow and write freeform?

Skip it for short, low-stakes documents where reader ambiguity carries little risk. The full three-stage process is most valuable for substantial docs like RFCs, PRDs, and decision docs that many stakeholders will read.