doc-coauthoring

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

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/ludotype/game-adventurertown --skill doc-coauthoring-ludotype
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/ludotype/game-adventurertown/tree/main/.agent/skills/doc-coauthoring
Command: npx skills add https://github.com/ludotype/game-adventurertown --skill doc-coauthoring-ludotype

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 doc. ## 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. - Reader Testing: Predicts questions real readers would ask and verifies the document answers them, catching ambiguity, false assumptions, and contradictions. - Use Case: You need to write a decision doc for a technical migration. The Skill gathers your context, helps you draft each section iteratively, then tests the final doc with a fresh reviewer to ensure it stands on its own. ## Quick Start Ask the assistant to guide you through writing a design doc 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 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 blind spots.

How to structure a decision doc or technical proposal?▼

Start with the section containing the most unknowns, usually the core proposal or technical approach, and leave summary sections for last. For each section, brainstorm candidate points, curate what to keep, draft, then refine through targeted edits.

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.

How do I test whether my document is clear to readers?▼

Use reader testing: generate 5-10 questions a real reader would ask, then have a fresh AI instance with no prior context answer them using only the document. Wrong answers or flagged ambiguities reveal gaps to fix.

What are the limitations of AI-assisted document drafting?▼

The author remains responsible for factual accuracy, links, and technical details, so a final human read-through is required. The workflow also takes longer than freeform drafting, though stages can be skipped if speed matters more.