doc-coauthoring

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

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Cramer-69/skills-repository-3af2d1c7 --skill doc-coauthoring-cramer-69
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/Cramer-69/skills-repository-3af2d1c7/tree/main/packages/claude/skills/doc-coauthoring
Command: npx skills add https://github.com/Cramer-69/skills-repository-3af2d1c7 --skill doc-coauthoring-cramer-69

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and technical specs alone often leads to blind spots, unclear structure, and documents that confuse readers. This Skill provides a structured three-stage workflow that turns document writing into a guided collaboration, ensuring the final doc actually works for its intended audience. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through targeted questions and info dumps before drafting begins. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates content with the user, and iteratively drafts using artifacts or markdown files. - Reader Testing: Validates the finished document with a fresh Claude instance (via sub-agents or manual testing) 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 context from Slack threads and shared docs, drafts each section through brainstorming and curation, then tests the doc with a context-free reader to verify clarity before sharing with the team. ## Quick Start Ask Claude to help you write a design doc or proposal 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 Claude?▼

Start by describing the document type, audience, and desired impact, then dump all relevant context. Claude asks clarifying questions, brainstorms content per section, drafts iteratively, and tests the final doc with a fresh reader to catch blind spots.

What is the doc co-authoring workflow process?▼

The workflow has three stages: Context Gathering (collecting background and constraints), Refinement & Structure (drafting section by section through brainstorming and curation), and Reader Testing (validating the doc with a context-free Claude instance).

Can this workflow use content from Slack or Google Docs?▼

Yes, if integrations or MCP servers are available, the workflow can pull context directly from messaging apps and document storage. Without integrations, you can paste content manually or enable connectors in Claude settings.

How does reader testing work for documents?▼

Reader testing predicts 5-10 questions real readers would ask, then tests them against a fresh Claude instance with no prior context. In Claude Code this uses sub-agents automatically; on claude.ai you paste the doc into a new conversation manually.

When should I skip the structured workflow and write freeform?▼

Freeform writing suits short or informal documents where structured iteration adds overhead. The workflow is designed for substantial docs like PRDs, RFCs, and specs where reader clarity and completeness matter.