How do I install the Doc Coauthoring skill?

Run npx skillmds add majiayu000/doc-coauthoring-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Doc Coauthoring safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Doc Coauthoring?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Doc Coauthoring free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Doc Coauthoring?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Doc Coauthoring by majiayu000 — Agent Skill

Name: Doc Coauthoring
Rating: 4.5 (4 reviews)
Author: majiayu000

Doc Coauthoring

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.

majiayu000 d5bd55b 2 files · 2.7 KB Updated Sep 9, 2026 567 repo stars

File contents

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"
User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC"
User seems to be starting a substantial writing task

Three Stages

Stage 1: Context Gathering

Goal: Close the gap between what the user knows and what Claude knows.

Initial Questions:

What type of document is this?
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?

Encourage the user to dump all context they have: background, discussions, why alternatives aren't being used, organizational context, timeline, technical dependencies.

Stage 2: Refinement & Structure

Goal: Build the document section by section through brainstorming, curation, and iterative refinement.

For each section:

Ask clarifying questions about what to include
Brainstorm 5-20 options
User indicates what to keep/remove/combine
Draft the section
Refine through surgical edits

Start with whichever section has the most unknowns.

Stage 3: Reader Testing

Goal: Test the document with a fresh perspective to catch blind spots.

Predict reader questions
Test with a sub-agent (no context bleed)
Run additional checks for ambiguity, false assumptions, contradictions
Fix any gaps identified

Tips for Effective Guidance

Be direct and procedural
Always give user agency to adjust the process
Don't let context gaps accumulate
Quality over speed

---name: doc-coauthoring-3description: 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" - User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC" - User seems to be starting a substantial writing task ## Three Stages ### Stage 1: Context Gathering **Goal:** Close the gap between what the user knows and what Claude knows. **Initial Questions:** 1. What type of document is this? 2. Who's the primary audience? 3. What's the desired impact when someone reads this? 4. Is there a template or specific format to follow? 5. Any other constraints or context? Encourage the user to dump all context they have: background, discussions, why alternatives aren't being used, organizational context, timeline, technical dependencies. ### Stage 2: Refinement & Structure **Goal:** Build the document section by section through brainstorming, curation, and iterative refinement. For each section: 1. Ask clarifying questions about what to include 2. Brainstorm 5-20 options 3. User indicates what to keep/remove/combine 4. Draft the section 5. Refine through surgical edits Start with whichever section has the most unknowns. ### Stage 3: Reader Testing **Goal:** Test the document with a fresh perspective to catch blind spots. 1. Predict reader questions 2. Test with a sub-agent (no context bleed) 3. Run additional checks for ambiguity, false assumptions, contradictions 4. Fix any gaps identified ## Tips for Effective Guidance - Be direct and procedural - Always give user agency to adjust the process - Don't let context gaps accumulate - Quality over speed

Frequently asked questions