doc-coauthoring

Guide documentation co-authoring through context gathering, refinement, and reader testing.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/yeeehaooo/agent-kit --skill doc-coauthoring-yeeehaooo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/yeeehaooo/agent-kit/tree/main/.claude/skills/doc-coauthoring
Command: npx skills add https://github.com/yeeehaooo/agent-kit --skill doc-coauthoring-yeeehaooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide users through a structured, three-stage workflow for co-authoring documentation. It helps teams transfer context, refine content through iteration, and verify that the document works for readers. The skill is triggered when users mention writing documentation, proposals, technical specs, decision docs, or similar tasks.

Core Features & Use Cases

  • Three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing.
  • Trigger conditions: When users reference writing docs, proposals, specs, RFCs, or similar tasks.
  • Stage 1 — Context Gathering: asks clarifying questions, enables a comprehensive context dump, and defines exit criteria.
  • Stage 2 — Refinement & Structure: builds sections through brainstorming, editing, and gap checks with iterative refinement.
  • Stage 3 — Reader Testing: tests the draft with a fresh context to surface blind spots before broad review.
  • Artifacts and scaffolds: creates outlines or templates to structure the document before drafting.

Quick Start

Offer the 3-stage doc co-authoring workflow to the user. If the user accepts, begin Stage 1 (Context Gathering) and collect context through guided questions. If they decline, proceed with freeform writing.

Frequently Asked Questions about doc-coauthoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a structured co-authoring workflow for technical documentation?

A structured co-authoring workflow guides teams through context gathering, refinement and structure, and reader testing to produce technical specs and proposals collaboratively.

How do I start writing technical specs using a co-authoring process?

Start writing technical specs by entering context gathering, where you answer clarifying questions and define exit criteria before moving to refinement and structure.

Can I use this workflow for writing decision records and RFCs?

Yes, you can use this co-authoring workflow for decision records and RFCs, as it triggers when users mention writing proposals, specs, or similar collaborative documents.

What is the best way to test documentation drafts for blind spots?

The best way to test documentation drafts for blind spots is reader testing with a fresh context, which surfaces hidden issues before broad review.

Does the documentation co-authoring workflow require any specific tools or dependencies?

The documentation co-authoring workflow requires no specific tools or dependencies, operating as a guided process using scaffolds and templates to organize content.