doc-coauthoring

Guide structured document coauthoring from context collection to reader effectiveness testing.

190|27|Updated Apr 22, 2026

Search Tags:#PRD #RFC #structured writing #reader testing #iterative drafting #document collaboration #proposal writing

Ready to run

npx skills add https://github.com/linxuan-sys/opencode-skills-chinese --skill doc-coauthoring-linxuan-sys

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/linxuan-sys/opencode-skills-chinese/tree/main/doc-coauthoring
Command: npx skills add https://github.com/linxuan-sys/opencode-skills-chinese --skill doc-coauthoring-linxuan-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps users produce structured, reader-effective documents by orchestrating a collaboration workflow from context gathering to iterative drafting and validation.

Core Features & Use Cases

Context-first alignment: Collects document type, audience, goals, constraints, and relevant background to close the gap between what the author knows and what the model/reader needs.
Iterative structured drafting: Builds documents part-by-part using clarification questions, brainstorm options, keep/delete/merge planning, gap checks, drafting, and precise editing.
Reader effectiveness testing: Validates the final document by testing it with a fresh model (no prior context) to surface ambiguities and missing assumptions.

Quick Start

Describe the document you want to write and who the audience is, then ask to use the document collaboration workflow.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema

How do I coauthor a PRD or RFC with structured drafting and reader testing?▼

Structured document collaboration uses context collection, iterative part-by-part drafting, and a final no-context reader test to coauthor PRDs and RFCs, validating reader effectiveness. It guides brainstorming, gap checks, and precise editing to ensure shared understanding.

What is reader effectiveness testing for technical specifications and decision docs?▼

Reader effectiveness testing validates technical specifications and decision docs by testing the final document with a fresh model that has no prior context. It surfaces ambiguities and missing assumptions to detect gaps that hinder accurate communication.

How do I start collaborative proposal writing when the author and reader have different context levels?▼

Collaborative proposal writing starts with context-first alignment, collecting document type, audience, goals, constraints, and relevant background. This closes the gap between author knowledge and reader needs before iterative drafting begins.

Can I use iterative drafting to build design documents part-by-part?▼

Iterative drafting builds design documents part-by-part through targeted clarification questions, brainstorm options, keep/delete/merge planning, gap checks, and precise editing. This structured approach ensures each section meets audience and goal requirements.

When do I need structured document collaboration for creating technical specifications?▼

Structured document collaboration is needed for technical specifications when accurate communication and shared understanding matter. It applies to creating PRDs, RFCs, proposals, and decision docs where reader gaps and ambiguities must be detected and resolved.

Does doc collaboration work for proposal writing without predefined templates?▼

Document collaboration guides proposal writing without predefined templates by orchestrating a three-phase process: context collection, iterative structured drafting, and reader effectiveness testing. It builds structure dynamically based on audience, goals, and constraints.