This is a structured workflow for writing docs with Claude that actually makes the process less painful. It walks you through three stages: dumping all your context while Claude asks clarifying questions, building the doc section by section through brainstorming and iteration, and testing it with a fresh Claude instance to catch gaps before real people see it. The context gathering phase is smart about pulling from Slack, Google Docs, or wherever your information lives. What I like here is the recognition that good documentation requires closing the knowledge gap first, then iterating on structure, not trying to do both at once. If you write specs, RFCs, or decision docs regularly, this gives you a repeatable process instead of staring at a blank page.

skills.sh installs
202
GitHub stars
476
last updated
Aug 21, 2026

Install

$ npx -y skills add aiskillstore/marketplace --skill doc-coauthoring --agent claude-code

Installs into .claude/skills of the current project.

Files

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:

  1. Context Gathering: User provides all relevant context while Claude asks clarifying questions
  2. Refinement & Structure: Iteratively build each section through brainstorming and editing
  3. 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.

Sponsors

Details

Repository
github.com/aiskillstore/marketplace
Categories
Documentation, Productivity & Planning, Automation & Workflows
First seen
Jun 3, 2026

More from aiskillstore/marketplace

All 37
1epicenterhq avatardocumentationepicenterhq/epicenterIn-code documentation, folder READMEs, code comments. Use when: "document this", "add JSDoc", "write a README", "explain this code", or writing README.md/JSDoc.188skills.sh installs
2longbridge avatargenerate-component-documentationlongbridge/gpui-componentGenerate documentation for new components. Use when writing docs, documenting components, or creating component documentation.172skills.sh installs
3thebushidocollective avatarstorybook-component-documentationthebushidocollective/hanUse when creating or improving component documentation in Storybook. Helps generate comprehensive docs using MDX, autodocs, and JSDoc comments.165skills.sh installs
4NVIDIA avatardoca-programming-guideNVIDIA/skillsUse this skill when the user is writing their first DOCA app or asking a library-agnostic programming question — picking a shipped sample to copy and modify, wi151skills.sh installs
5jezweb avatargemini-guidejezweb/claude-skillsLook up Gemini API documentation, SDK patterns, and current best practices when building with Google Gemini. Maps topics to local cached docs and live sources, 149skills.sh installs
6EpicenterHQ avatardocumentationEpicenterHQ/epicenterIn-code documentation, folder READMEs, and code comments. Use when writing README.md files, JSDoc comments, or explaining code organization.0skills.sh installs