Doc Coauthoring
- 41 installs
- 82 repo stars
- Updated August 2, 2026
- aaaaqwq/claude-code-skills
doc-coauthoring is a Claude Code skill that guides a structured workflow for co-authoring documentation such as specs, proposals, and decision docs.
About
This Claude Code skill guides a structured workflow for co-authoring documentation such as technical specs, proposals, decision docs, and guides. The guide (written in Chinese) breaks the work into context transfer, content iteration, and reader verification phases. A developer uses it to efficiently draft and refine structured documents with the agent.
- Structured three-phase workflow for co-authoring documentation: context transfer, iteration, verification
- Covers technical specs, proposals, decision docs (ADRs), and guides
- Best practices for clear heading hierarchy, example-first writing, and iterative revision (Chinese-language guide)
Doc Coauthoring by the numbers
- 41 all-time installs (skills.sh)
- Ranked #863 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
doc-coauthoring capabilities & compatibility
Free; a prompt-only workflow with no dependencies
- Capabilities
- doc authoring · spec writing · proposal writing · adr writing
- Use cases
- documentation
- Pricing
- Free
What doc-coauthoring says it does
Guide users through a structured workflow for co-authoring documentation.
npx skills add https://github.com/aaaaqwq/claude-code-skills --skill doc-coauthoringAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 41 |
|---|---|
| repo stars | ★ 82 |
| Last updated | August 2, 2026 |
| Repository | aaaaqwq/claude-code-skills ↗ |
What it does
Co-author technical docs, proposals, or decision records through a structured context-iteration-verification workflow.
Who is it for?
Developers co-authoring technical specs, proposals, or decision docs with an agent
Skip if: Prose or marketing copy unrelated to structured technical documentation
When should I use this skill?
You want to write documentation, proposals, technical specs, or decision docs in a structured way
What you get
A structured document refined through iteration and verified against its readers
- Structured documentation
- Technical specs
- Proposals
By the numbers
- 3-phase workflow (context transfer, iteration, verification)
- 4 document types (spec, proposal, decision, guide)
Files
文档协作工作流
当使用此技能
- 编写技术文档
- 创建项目提案
- 起草技术规范
- 决策文档
- 结构化内容创作
工作流程
阶段 1: 上下文转移
- 收集需求和背景
- 确定受众和目标
- 列出关键要点
阶段 2: 内容迭代
- 初稿: 快速写出核心内容
- 完善: 添加细节和示例
- 审核: 检查逻辑和流畅性
阶段 3: 验证
- 受众测试: 是否易于理解
- 完整性: 是否遗漏关键信息
- 可行性: 是否可执行
文档类型
- 技术规范: API 文档、架构设计
- 提案: 项目计划、功能建议
- 决策: ADR、技术选型
- 指南: 教程、手册
最佳实践
- 结构化: 使用清晰的标题层次
- 示例优先: 用代码/示例说明
- 迭代优化: 多次修订完善
触发词
- "写文档"
- "创建提案"
- "起草规范"
- "决策文档"
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.451k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.391k15.9kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.387k15.9k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k72Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k72
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.267k192kFAQ
What document types does it cover?
Technical specs, proposals, decision docs (ADRs), and guides.
What are the workflow phases?
Context transfer, content iteration (draft, refine, review), and verification for the reader.