doc-coauthoring is Anthropic’s agent skill for writing documentation, proposals, technical specs, decision docs, PRDs, RFCs and similar structured content together with Claude. When a user starts a substantial writing task, Claude offers a structured workflow and, if the user accepts, acts as an active guide through three stages: Context Gathering, Refinement and Structure, and Reader Testing. A user who declines works freeform.
The skill closes the gap between what the author knows and what Claude knows before anything is drafted, then builds the document one section at a time: clarifying questions, 5-20 brainstormed options, the user’s keep, remove or combine choices, a gap check, a draft and surgical edits. Before the document goes to other people, it is tested on a fresh Claude with no context from the conversation, to catch the blind spots that make sense to the authors but confuse readers.
What You Get
- A trigger that offers the workflow when a user mentions writing a doc, proposal, spec, PRD, design doc, decision doc or RFC, with a freeform fallback if they decline
- A context-gathering stage with five meta-questions, an encouraged info dump and 5-10 numbered clarifying questions that can be answered in shorthand
- A per-section loop: clarifying questions, 5-20 brainstormed options, keep/remove/combine curation, a gap check, drafting and surgical refinement
- A document scaffold with placeholder text for every section, created as an artifact or as a markdown file in the working directory
- A reader-testing stage that runs predicted reader questions against a fresh Claude, via sub-agents where available or by hand in claude.ai
- A final whole-document review for flow, redundancy, contradictions and generic filler, plus closing tips on appendices and updating from reader feedback
Common Use Cases
- Drafting a technical spec or design doc from scattered notes, chat threads and shared documents
- Writing a decision doc or proposal where the core recommendation has the most unknowns and needs to be worked out first
- Following a team’s existing template for a PRD or RFC while filling each section with the right context
- Checking that a finished document answers readers’ questions before it is circulated, including readers who paste it into Claude
What Makes It Unique
Where frontend-design and pdf in the same repository shape Claude’s output for interfaces and files, doc-coauthoring shapes the conversation itself: it is a facilitation script that tells Claude when to ask, when to brainstorm and when to wait for the user, and it treats the user’s numbered selections and direct feedback as a way to learn their style for later sections. Its distinctive step is Reader Testing, where the document is handed to a Claude with no context from the session, so the doc is judged by someone who only has the page, much as a colleague would be.
Under The Hood
The skill is a single SKILL.md of instructions with no scripts or reference files. When it loads, Claude follows the staged workflow in conversation. For drafting it creates a scaffold with placeholder text, either as an artifact with create_file or, without artifacts, as a markdown file in the working directory such as decision-doc.md, and edits each section in place with str_replace rather than reprinting the document. When the user points to team channels or shared documents, it uses whatever integrations are connected, such as Slack, Teams, Google Drive or SharePoint, and asks before searching connected tools for unknown projects; without them it asks the user to paste content or enable connectors. For reader testing in Claude Code it invokes sub-agents with only the document and each question; in claude.ai it gives the user steps to test in a fresh conversation. It runs no commands of its own.