doc-coauthoring

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

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/prabaljainn/my-claude-code-setup --skill doc-coauthoring-prabaljainn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/prabaljainn/my-claude-code-setup/tree/main/claude/skills/doc-coauthoring
Command: npx skills add https://github.com/prabaljainn/my-claude-code-setup --skill doc-coauthoring-prabaljainn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and technical specs alone often produces docs that make sense to the author but confuse readers. This Skill structures co-authoring into three stages so context is fully transferred, each section is deliberately refined, and blind spots are caught before others read the doc. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through structured questions and info dumps, optionally pulling from connected tools like Slack or Google Drive. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates them with the user, drafts into an artifact or markdown file, and iterates with surgical edits. - Reader Testing: Tests the finished doc with a fresh Claude instance (sub-agent or new conversation) to expose ambiguity, false assumptions, and contradictions. - Use Case: Draft a decision doc for a technical migration: dump your context, build each section through curated brainstorming, then verify a fresh reader can answer realistic questions about the doc. ## Quick Start Ask Claude to help you write a design doc or proposal using the doc-coauthoring workflow and answer its initial context questions.

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 design doc with Claude?▼

Start the doc-coauthoring workflow and answer initial questions about doc type, audience, and desired impact. Claude then gathers your context, builds each section through brainstorming and curation, and tests the final doc with a fresh reader before completion.

How to test if my documentation is clear to readers?▼

Use reader testing: generate 5-10 questions a real reader would ask, then have a fresh Claude instance with no prior context answer them using only the document. Wrong answers or flagged ambiguities reveal gaps to fix before publishing.

Can Claude pull context from Slack or Google Drive when drafting docs?▼

Yes, if connectors or MCP integrations are enabled, the workflow reads shared documents and team channels directly during context gathering. Without integrations, you paste the relevant content manually into the conversation.

What types of documents does this workflow support?▼

It supports technical specs, decision docs, PRDs, RFCs, proposals, and similar structured content. The workflow adapts its section suggestions based on the document type and any template you provide.

When should I skip the structured doc workflow?▼

Skip it for short or low-stakes writing where three stages of gathering, refinement, and testing add unnecessary overhead. You can decline the initial offer and work freeform, or skip individual stages at any time.