doc-coauthoring

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

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/taylorelley/skills --skill doc-coauthoring-taylorelley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/taylorelley/skills/tree/main/skills/workflow/doc-coauthoring
Command: npx skills add https://github.com/taylorelley/skills --skill doc-coauthoring-taylorelley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and specs alone often produces docs full of blind spots, missing context, and sections that confuse readers. This Skill structures the co-authoring process so the final document actually works for its intended audience. ## 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). - Iterative Section Drafting: Brainstorms 5-20 options per section, lets you curate what stays, then drafts and refines through surgical edits. - Reader Testing: Predicts questions real readers would ask and checks the document for ambiguity, false assumptions, and contradictions before others read it. - 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 whether a fresh reader can correctly answer questions using only the doc. ## Quick Start Help me write a technical design doc for our new caching layer using the doc 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 design doc with AI assistance?

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

How to structure a decision doc or RFC?

Start by defining the doc type, audience, and desired impact, then build 3-5 sections appropriate for the doc type. Begin with the section containing the most unknowns, usually the core proposal, and leave summary sections for last.

Can this workflow use content from Slack or Google Docs?

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

What is reader testing for documentation?

Reader testing validates a document by having a fresh reviewer with no prior context answer predicted reader questions using only the doc. It surfaces ambiguity, false assumptions, and contradictions that authors miss because they already know the background.

When should I skip the structured doc workflow?

Skip it for short or low-stakes writing where a three-stage process adds overhead. The workflow is designed for substantial documents like specs, proposals, and decision docs where reader comprehension matters; you can always choose to work freeform instead.