doc-coauthoring

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

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/whatswithavi/Ecchelon_project --skill doc-coauthoring-whatswithavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/whatswithavi/Ecchelon_project/tree/main/.agent/skills/doc-coauthoring
Command: npx skills add https://github.com/whatswithavi/Ecchelon_project --skill doc-coauthoring-whatswithavi

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, content is refined section by section, and blind spots are caught before others read the document. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through structured questions and info dumps, optionally pulling from connected tools like Slack or Google Drive. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates them with the user, drafts content, and iterates with surgical edits via artifacts or files. - Reader Testing: Tests the finished document with a fresh AI instance (sub-agent or new conversation) to detect ambiguity, false assumptions, and contradictions. - Use Case: A product manager drafting a decision doc uses this workflow to dump project context, build each section iteratively, then verify a fresh reader can answer realistic questions about the proposal before sharing it with stakeholders. ## Quick Start Ask the assistant to guide you through the doc co-authoring workflow to draft a technical spec 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 decision 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 curation, and finally test the draft with a fresh AI conversation to catch blind spots before sharing.

What is the best workflow for drafting technical specs collaboratively?▼

A three-stage approach works well: context gathering to close knowledge gaps, section-by-section refinement with iterative edits, and reader testing where a context-free reader attempts to answer realistic questions from the document alone.

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

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

How does reader testing catch documentation blind spots?▼

Reader testing gives the document to a fresh AI instance with no prior conversation context, then asks realistic reader questions. Misinterpretations, assumed knowledge, and contradictions surface as wrong or uncertain answers, which you then fix.

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

Skip the workflow for short or low-stakes documents where three stages of iteration cost more time than they save. The workflow is designed for substantial documents like specs, proposals, and decision docs that many readers will depend on.