doc-coauthoring

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

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/eklyukin/my-ai-config --skill doc-coauthoring-eklyukin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/eklyukin/my-ai-config/tree/main/skills/doc-coauthoring
Command: npx skills add https://github.com/eklyukin/my-ai-config --skill doc-coauthoring-eklyukin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, specs, and proposals 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 deliberately refined, and blind spots are caught before others read the document. ## Core Features & Use Cases - Three-Stage Workflow: Context Gathering with clarifying questions, section-by-section Refinement with brainstorming and curation, and Reader Testing with a fresh context-free reviewer. - Iterative Section Drafting: Brainstorms 5-20 options per section, curates based on user feedback, and drafts into an artifact or markdown file using surgical edits. - Reader Testing: Predicts questions real readers would ask and validates the document against them using sub-agents or a fresh conversation to expose ambiguity and assumed knowledge. - Use Case: Draft a technical decision doc by dumping project context, curating brainstormed points for each section, then verifying a fresh reader can answer key questions correctly before sharing with the team. ## Quick Start Help me write a decision doc for our migration plan using the structured co-authoring 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 technical spec or decision doc with AI assistance?▼

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

How to test whether a document is clear to readers?▼

Predict 5-10 questions real readers would ask, then have a fresh AI instance with no prior context answer them using only the document. Incorrect answers or flagged ambiguities reveal gaps to fix before publishing.

Can this workflow use content from Slack or shared documents?▼

Yes, if integrations or MCP servers for tools like Slack, Google Drive, or SharePoint are available, the workflow can pull context directly from channels and documents. Without integrations, paste the relevant content manually.

What document types does the co-authoring workflow support?▼

It supports structured documents such as technical specs, decision docs, PRDs, RFCs, proposals, and design docs. The workflow adapts section suggestions based on the document type and any provided template.

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

Skip it for short or low-stakes writing where three stages of iteration add overhead without benefit. The workflow is designed for substantial documents that multiple readers will rely on, and you can decline it at the initial offer.