# Why does long document work need its own skill?

Canonical URL: https://bestskillsforclaude.com/en/skills/doc-coauthoring
Language: en
Skill: doc-coauthoring
Publisher: Anthropic (https://github.com/anthropics)
Source: https://github.com/anthropics/skills/tree/main/skills/doc-coauthoring
License as stated by the publisher: Apache 2.0
Runtime: Claude apps and Claude Code
Category: Document work
Last reviewed: 2026-08-05

Because one prompt and one long answer is the worst way to write anything that matters.

## Short answer
The doc-coauthoring skill turns document writing into a staged collaboration: agree the shape, draft in parts, and revise against what was agreed. It is worth loading for documents long enough that a single generated draft would be unreviewable, such as specifications, proposals and policies.

Best for: Specifications, proposals, policies and reports that a human has to defend afterwards.
Skip it if: You need a short piece of copy, where the extra structure costs more than it returns.

## What to remember
- It front loads the disagreement into the outline, which is the cheapest place to have it.
- Section by section drafting keeps every part reviewable at human speed.
- It pairs naturally with docx when the deliverable has to be a Word file.
- It structures the work. It does not know your subject matter for you.

## What it changes in practice
The usual failure with long documents is that a model produces twenty pages in one pass. It reads fluently, so nobody reviews it properly, and the errors surface later in front of a customer or a regulator.
Working in stages changes the economics. Fixing an outline takes minutes, fixing a section takes an hour, and fixing a finished document that everyone already approved takes a week.

## Where it disappoints
It is overhead on short work. For a paragraph of marketing copy the ceremony is pure cost, and a direct request is better.
It also cannot supply judgement you do not have. If nobody on your side knows what the document should claim, a better process only produces a well structured guess.

## Install and first run
1. Install the skill from anthropics/skills, published under Apache 2.0.
2. Start with the outline and argue about it before any prose is written.
3. Draft one section at a time and review it before moving on, so mistakes stay local.

## Questions
### How is this different from just asking for a document?
It splits the work into outline, drafting and revision with review points, instead of producing one long draft nobody checks.

### Does it produce Word files?
Not by itself. Pair it with the docx skill when the final artifact has to be a .docx file.

### What license is it under?
Apache 2.0, unlike the docx, xlsx, pptx and pdf skills, which are source available.

## Sources
- anthropics/skills on GitHub: https://github.com/anthropics/skills
- anthropics/skills, doc-coauthoring skill directory: https://github.com/anthropics/skills/tree/main/skills/doc-coauthoring

## Other languages
- Spanish: https://bestskillsforclaude.com/es/skills/doc-coauthoring
- Brazilian Portuguese: https://bestskillsforclaude.com/pt-br/skills/doc-coauthoring
- Japanese: https://bestskillsforclaude.com/ja/skills/doc-coauthoring