doc-coauthoring

doc-coauthoring is a skill for Claude Code, Codex from thevibeworks/claude-code-docs. It costs 77 tokens per session (3,254 once invoked), scanned A, a copy of doc-coauthoring, MIT.

A guided process for writing documentation, proposals, technical specifications, and decision records. It covers gathering context, refining the structure, and testing the document with a fresh reader.

In plain words
What is it for?
Use it to co-write RFCs, design documents, decision documents, proposals, specifications, and other structured technical documents.
Why use it?
It helps uncover missing information and unclear sections before a document is shared. It also gives longer writing tasks a repeatable process.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions Claude Code.

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/thevibeworks/claude-code-docs/doc-coauthoring
Any agent
npx skills add thevibeworks/claude-code-docs --skill doc-coauthoring
Clone the repo
git clone --depth 1 https://github.com/thevibeworks/claude-code-docs

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for doc-coauthoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/doc-coauthoring.svg)](https://agentmods.dev/skills/thevibeworks/claude-code-docs/doc-coauthoring)
Your own site
<a href="https://agentmods.dev/skills/thevibeworks/claude-code-docs/doc-coauthoring"><img src="https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/doc-coauthoring.svg" alt="Measured on agentmods" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,254 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.03254
Opus 5 $0.00039 $0.01627
Sonnet 5 $0.00015 $0.00651
Haiku 4.5 $0.00008 $0.00325

Measured 2d ago against content hash 2e47d78846fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

doc-coauthoring scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to doc-coauthoring — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

content/github/skills/skills/doc-coauthoring/SKILL.md · 376 lines

How it starts

The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

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:

  1. What type of document is this? (e.g., technical spec, decision doc, proposal)
  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 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

Read the full file on GitHub · 376 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 376 lines · 77 tokens per session scan A 2e47d78846fa

Subscribe to this mod's changes

doc-coauthoring is a skill published in the GitHub repository thevibeworks/claude-code-docs (39 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 3,254 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to doc-coauthoring, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

sync

Synchronize task files and source-of-truth documents. Update NEXT-TASKS.md, FUTURE-ENHANCEMENTS.md, README, and CHANGELOG to reflect current project state.

cortex-tms/cortex-tms · 40 tokens

validate

Run the full quality gate — tests, lint, build, and cortex-tms validate --strict.

cortex-tms/cortex-tms · 22 tokens

vibing-orchestrate

Run several independent tasks in parallel by creating worker vibing.nvim chats, handing each one a self-contained brief, and aggregating their results. Use when the user asks for parallel work ("do these three in parallel", "split this across separate chats", "並行でやって", "この2つを別々のチャットで").

shabaraba/vibing.nvim · 76 tokens

self-testing

E2E self-testing workflow for vibing.nvim using a separate Neovim instance controlled over RPC. Use when writing or debugging E2E tests, running npm run test:e2e, or executing the 3-try auto-fix rule after implementing a feature. Covers the…

shabaraba/vibing.nvim · 105 tokens

test-design

Automatically design comprehensive E2E test cases for newly implemented vibing.nvim features. Use immediately after completing feature implementation (Phase 5.4) and before running E2E tests. Generates test scenarios covering Happy paths, Error cases, Edge cases, and Integration points with priority ranking…

shabaraba/vibing.nvim · 82 tokens

vibing-chat-search

Use when the user wants to find a past vibing.nvim conversation by topic — phrases like "前に〜について聞いたことあったっけ", "did we talk about X before", "find that chat where I asked about Y". Searches every chat file under .vibing/chat/ (both User and Assistant content) for a natural-language query, narrows candidates with grep…

shabaraba/vibing.nvim · 116 tokens