doc-coauthoring

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

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Syedyasir001/RVULibPass --skill doc-coauthoring-syedyasir001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/Syedyasir001/RVULibPass/tree/main/.agent/skills/library/doc-coauthoring
Command: npx skills add https://github.com/Syedyasir001/RVULibPass --skill doc-coauthoring-syedyasir001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and specs alone often leads to blind spots, missing context, and documents that confuse readers. This Skill provides a structured three-stage workflow that closes the context gap between you and the AI, builds each section iteratively, and validates the final document with fresh-reader testing. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through guided questions and info dumps, with support for pulling content from connected tools like Slack or Google Drive. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates content with your feedback, and drafts iteratively using artifacts or markdown files. - Reader Testing: Tests the finished document with a fresh AI instance (via sub-agents or a manual fresh conversation) to catch ambiguities, false assumptions, and contradictions before others read it. - Use Case: You need to write a decision doc for a technical migration. The workflow gathers your team context, drafts each section through brainstorming and curation, then verifies a fresh reader can correctly answer likely questions about the doc. ## Quick Start Ask the AI to guide you through the doc co-authoring workflow to write a technical design doc for your upcoming project.

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 technical design doc with AI assistance?▼

Use a structured co-authoring workflow: first dump all project context while the AI asks clarifying questions, then build each section through brainstorming and iterative drafting, and finally test the doc with a fresh AI conversation to catch blind spots before sharing it.

How to test if my document is clear to readers?▼

Reader testing validates clarity by having a fresh AI instance with no prior context answer predicted reader questions about your document. If it misinterprets content or flags ambiguities, you revise those sections and retest until answers are consistently correct.

Can this workflow pull context from Slack or Google Drive?▼

Yes, if integrations or MCP servers are available, the workflow can read team channels, threads, and shared documents directly during context gathering. Without integrations, you can paste content manually or enable connectors in your Claude settings.

What types of documents work with a co-authoring workflow?▼

The workflow supports technical specs, decision docs, PRDs, RFCs, proposals, and similar structured content. It adapts section suggestions based on the document type and any template you provide.

When should I skip the structured workflow and write freeform?▼

Freeform writing suits short or low-stakes documents where reader testing adds little value. The structured workflow is most useful for substantial documents that multiple stakeholders will read and act on, where blind spots are costly.