Localized reading guide
doc-coauthoringPurpose, usage and source
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Source retrieved:
- Source repository
- anthropics/skills
- SKILL.md
skills/doc-coauthoring/SKILL.md- Repository stars
- 185,373
- Repository updated
- 2026-10-29
- Categories
- Documents
- Last collected
License: Unspecified
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
How the upstream workflow works
Doc Co-Authoring Workflow
This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.
Upstream passage · L6 ↗When to Offer This Workflow
User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up" User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC" User seems to be starting a substantial writing task Initial offer: Offer the user a structured workflow for co-authoring the document. Explain the three stages:
Upstream passage · L10 ↗Step 1: Clarifying Questions
Announce work will begin on the [SECTION NAME] section. Ask 5-10 clarifying questions about what should be included: Generate 5-10 specific questions based on context and section purpose. Inform them they can answer in shorthand or just indicate what's important to cover.
Upstream passage · L154 ↗Requirements and setup
Step 2: Setup Testing
Provide testing instructions: Open a fresh Claude conversation: https://claude.ai
Upstream passage · L300 ↗Limits and quality checks
Quality Checking
After 3 consecutive iterations with no substantial changes, ask if anything can be removed without losing important information. When section is done, confirm [SECTION NAME] is complete. Ask if ready to move to the next section.
Upstream passage · L215 ↗Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Doc Co-Authoring Workflow
- When to Offer This Workflow
- Stage 1: Context Gathering
- Initial Questions
- Info Dumping
- Stage 2: Refinement & Structure
- Step 1: Clarifying Questions
- Step 2: Brainstorming
- Step 3: Curation
- Step 4: Gap Check
- Step 5: Drafting
- Step 6: Iterative Refinement
- Quality Checking
- Near Completion
- Stage 3: Reader Testing
- Testing Approach
- Step 1: Predict Reader Questions
- Step 2: Test with Sub-Agent
- Step 3: Run Additional Checks
- Step 4: Report and Fix
- Step 1: Predict Reader Questions
- Step 2: Setup Testing
- Step 3: Additional Checks
- Step 4: Iterate Based on Results
- Exit Condition (Both Approaches)
- Final Review
- Tips for Effective Guidance
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
ca45fc496a3436251f191354091d557da31c15b5- Source SHA-256
2e47d78846faeea4a56e9809c52700087a15a2155a3f293a3efbaded81398ef4