doc-coauthoring

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

Updated May 18, 2026
One-click install
npx skills add https://github.com/fts-pro/FTS-MMIS-AFRIKA --skill doc-coauthoring-fts-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/fts-pro/FTS-MMIS-AFRIKA/tree/main/.agent/skills/doc-coauthoring
Command: npx skills add https://github.com/fts-pro/FTS-MMIS-AFRIKA --skill doc-coauthoring-fts-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and technical 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 and clarifying questions), Refinement & Structure (section-by-section brainstorming, curation, and drafting), and Reader Testing (validating the doc with a fresh, context-free reviewer). - Section-by-Section Drafting: Brainstorms 5-20 options per section, lets you curate what to keep, then drafts and refines through surgical edits using artifacts or markdown files. - Reader Testing: Predicts questions real readers would ask, tests the document against a fresh Claude instance or sub-agent, and loops back to fix ambiguities, contradictions, and assumed knowledge. - Use Case: You need to write a decision doc for a technical migration. The Skill gathers your full context, helps you draft each section iteratively, then verifies a fresh reader can correctly answer key questions from the doc alone. ## Quick Start Ask the assistant to guide you through the doc co-authoring workflow to draft a technical design document 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 the doc section by section through brainstorming and curation, and finally test the finished doc with a fresh reviewer to catch gaps.

How to draft a decision doc or RFC collaboratively?▼

Start with the section containing the most unknowns, usually the core proposal. Brainstorm 5-20 options per section, curate what to keep with brief justifications, then draft and refine through targeted edits rather than rewriting the whole document.

Can this workflow use content from Slack or Google Docs?▼

Yes, if integrations or MCP connectors are available, the workflow can pull context directly from team channels, threads, and shared documents. Without connectors, you can paste the relevant content manually into the conversation.

What is reader testing for documentation?▼

Reader testing validates a document by having a fresh reviewer with no prior context answer predicted reader questions. It surfaces ambiguities, assumed knowledge, and contradictions that authors miss because they already understand the material.

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

Freeform writing suits short or low-stakes documents where reader ambiguity carries little risk. The structured workflow pays off for substantial docs like specs and proposals that many stakeholders will read and act on.