AI Summarydoc-coauthoring guides users through a structured three-stage workflow (context gathering, refinement, and reader testing) for collaboratively creating technical documentation, proposals, and specs. It benefits technical writers, engineers, and product managers who need to efficiently co-author structured content.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "doc-coauthoring" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/doc-coauthoring && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/doc-coauthoring/SKILL.md "https://raw.githubusercontent.com/anthropics/skills/main/skills/doc-coauthoring/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
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.
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.
When to Offer This Workflow
Trigger conditions: • 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: • Context Gathering: User provides all relevant context while Claude asks clarifying questions • Refinement & Structure: Iteratively build each section through brainstorming and editing • Reader Testing: Test the doc with a fresh Claude (no context) to catch blind spots before others read it Explain that this approach helps ensure the doc works well when others read it (including when they paste it into Claude). Ask if they want to try this workflow or prefer to work freeform. If user declines, work freeform. If user accepts, proceed to Stage 1.
Stage 1: Context Gathering
Goal: Close the gap between what the user knows and what Claude knows, enabling smart guidance later.
Initial Questions
Start by asking the user for meta-context about the document: • What type of document is this? (e.g., technical spec, decision doc, proposal) • Who's the primary audience? • What's the desired impact when someone reads this? • Is there a template or specific format to follow? • Any other constraints or context to know? Inform them they can answer in shorthand or dump information however works best for them. If user provides a template or mentions a doc type: • Ask if they have a template document to share • If they provide a link to a shared document, use the appropriate integration to fetch it • If they provide a file, read it If user mentions editing an existing shared document: • Use the appropriate integration to read the current state • Check for images without alt-text • If images exist without alt-text, explain that when others use Claude to understand the doc, Claude won't be able to see them. Ask if they want alt-text generated. If so, request they paste each image into chat for descriptive alt-text generation.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster