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.

by ThinkInAIXYZ 6.2k GitHub stars Apache-2.0 Updated Aug 18, 2026
doc-coauthoring skill by ThinkInAIXYZ
Social preview for ThinkInAIXYZ/deepchat

Overview

doc-coauthoring is an open-source docs skill for Claude Code and compatible agents, published by ThinkInAIXYZ. Its author describes it as: “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…”. The project has 6.2k stars on GitHub and is available under the Apache-2.0 license. Add it to your setup with `git clone https://github.com/ThinkInAIXYZ/deepchat ~/.claude/skills/doc-coauthoring`.

What doc-coauthoring does

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.

Best for

What’s inside

The SKILL.md for doc-coauthoring is organised into these sections:

  • 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

Installation

Add doc-coauthoring to your agent with:

git clone https://github.com/ThinkInAIXYZ/deepchat ~/.claude/skills/doc-coauthoring

Review a skill’s source before installing it — skills can instruct your agent to run commands. This command comes from the skill’s public repository, which is the source of truth for setup steps. New to skills? Read how to install Claude Code skills.

Supported agents

Neither the skill nor its repository names a specific agent. It uses the SKILL.md format, which several agents can load — check the repository for any agent-specific requirements.

License

doc-coauthoring is published under the Apache-2.0 license.

Strengths

  • Clear Apache-2.0 license — safe to read and adapt within its terms
  • Ships in ThinkInAIXYZ/deepchat, an established project with 6,228 GitHub stars
  • Actively maintained — repository updated in the last 90 days

Author

ThinkInAIXYZ 25 skills in the catalog · GitHub profile ↗
View skills

Topics

Need a skill like this, tailored to your team?Build a custom skill →

Frequently asked questions

What does doc-coauthoring do?
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 do I install doc-coauthoring?
Run git clone https://github.com/ThinkInAIXYZ/deepchat ~/.claude/skills/doc-coauthoring in your agent, then reload your skills. Review the source at https://github.com/ThinkInAIXYZ/deepchat before installing.
Is doc-coauthoring free to use?
Yes. doc-coauthoring is free and open source under the Apache-2.0 license, so you can read, run, and adapt it within that license's terms.
Where does doc-coauthoring come from?
doc-coauthoring ships inside ThinkInAIXYZ/deepchat, a repository that contains 25 catalogued skills in total. The repository's 6,228 GitHub stars apply to that whole collection, not to this skill on its own.

Related skills

More Docs skills →

Use only when a developer explicitly asks to clean, prune, tidy, or organize DeepChat SDD documentation after implementation and validation. Scans docs/features, docs/issues, and docs/architecture; prefers multi-agent review when available; removes completed issue docs when a linked GitHub issue is closed or implementation and validation evidence proves the bug no longer exists, drops stale plans and legacy task files from completed feature or architecture goals, and deletes obsolete feature or architecture docs.

6.2k GitHub stars Apache-2.0 Updated Aug 18, 2026 Free

Use before substantial DeepChat code, configuration, documentation, test, build, feature, issue, refactor, or architecture changes that need a durable RFC and an explicit execution path. Skip trivial style fixes, small localized logic changes, routine docs edits, and simple bugs unless the developer asks for SDD. Use plan.md as the only separate tracker when needed, default to implementation-first validation, and ask before optional GitHub issue sync unless the developer explicitly requested sync.

6.2k GitHub stars Apache-2.0 Updated Aug 18, 2026 Free

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

6.2k GitHub stars Apache-2.0 Updated Aug 18, 2026 Free

Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or health check, says LazyCodex, lazycodex-ai, omo-codex, or Codex behaves oddly after an install, update, or config change, suspects a stale, drifted, or broken setup, or wants the local install audited and compared with the latest LazyCodex and Codex code.

↑ GrowingActive CodexCursorOpenCode
69k GitHub stars Other Updated Sep 21, 2026 Free

Yao process documentation expert. ALWAYS invoke this skill when the user needs to discover available processes, read process signatures, or validate process names. Do not guess process APIs — use this skill first.

Claude Code
7.7k GitHub stars Other Updated Aug 18, 2026 Free