Language:JapaneseEnglish

doc-coauthoring Claude Code Skill

Author
Anthropic
Topics
Documents & Content Creation · Claude Code Customization & Workflow
First cataloged
2026-07-09 (UTC)
Explanation last updated
2026-08-21 (UTC)
Source (GitHub) last updated
2025-12-04 (UTC) (266 days ago)

The explanation below is AI-generated. Please verify it against the sources.

doc-coauthoring is a Claude skill that structures documentation writing into three stages: gathering background context, drafting and refining content section by section, and testing the finished document with a context-free Claude instance to catch confusing spots. During context gathering it asks clarifying questions and can pull in information from connected messaging or file-storage tools when those are available. In the drafting stage it brainstorms options for each section, lets the user pick what to keep, and edits a working file or artifact incrementally. In the final stage it either runs automated reader tests through sub-agents (in environments like Claude Code) or gives the user step-by-step instructions to test the document manually with a fresh Claude conversation. The overall goal described in the skill's instructions is a document that works well for its intended readers.

About the service

According to the skill's instructions, it can optionally use connectors or MCP servers for services such as Slack, Microsoft Teams, Google Drive, or SharePoint to fetch relevant conversations or existing documents during context gathering. This integration is not required; the workflow falls back to manual pasting of content when no such connections are available.

What you can do with doc-coauthoring

  • Follow a three-stage workflow (context gathering, drafting/refinement, reader testing) when writing docs, proposals, or specs
  • Get clarifying questions and brainstormed options for each section of the document
  • Have a draft built and edited incrementally as an artifact or markdown file
  • Pull background context from connected tools like Slack, Teams, Google Drive, or SharePoint when available
  • Test the finished document with a fresh Claude instance or sub-agent to surface unclear or missing information

Sources

Back to list