doc-coauthoring

Guides collaborative document creation through context gathering, iterative drafting, and reader testing.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Clay-HHK/claude-skills --skill doc-coauthoring-clay-hhk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/Clay-HHK/claude-skills/tree/main/doc-coauthoring
Command: npx skills add https://github.com/Clay-HHK/claude-skills --skill doc-coauthoring-clay-hhk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and technical specs alone often produces documents full of blind spots, missing context, and sections that confuse readers. This Skill structures the co-authoring process so the final document actually works for its intended audience. ## Core Features & Use Cases - Three-Stage Workflow: Guides users through Context Gathering, Refinement & Structure, and Reader Testing for any structured document. - Section-by-Section Drafting: Brainstorms 5-20 options per section, curates with the user, then drafts and iteratively refines using targeted edits. - Reader Testing: Validates the finished document with a fresh, context-free reviewer (sub-agent or manual test) to catch ambiguity, false assumptions, and contradictions. - Use Case: A product manager needs to write a decision doc for a new architecture. The Skill gathers project context, builds each section through brainstorming and curation, then tests the draft against realistic reader questions before stakeholders see it. ## Quick Start Ask the assistant to guide you through writing a technical spec or decision doc using the structured co-authoring workflow.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I write a technical spec or decision doc with AI assistance?▼

Use a structured co-authoring workflow: first dump all project context while the AI asks clarifying questions, then build each section through brainstorming and curation, and finally test the draft with a fresh reviewer to catch blind spots before sharing it.

How to test whether a document is clear for readers?▼

Predict 5-10 questions real readers would ask, then have a fresh AI instance with no prior context answer them using only the document. Incorrect answers or flagged ambiguities reveal gaps to fix before publication.

What document types does this workflow support?▼

The workflow supports documentation, proposals, technical specs, decision docs, PRDs, design docs, and RFCs. It adapts section structure and clarifying questions based on the document type and any template the user provides.

Can I skip stages of the co-authoring workflow?▼

Yes, the workflow explicitly gives users agency to skip stages or work freeform at any point. If a user declines the structured approach or wants to move faster, the assistant adjusts rather than forcing the full process.

Does the workflow work without artifacts or sub-agents?▼

Yes, it includes fallback paths: without artifacts it drafts into a markdown file in the working directory, and without sub-agents it instructs the user to manually test the document in a fresh conversation.