doc-coauthoring

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

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/pchemguy/AISandbox --skill doc-coauthoring-pchemguy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/pchemguy/AISandbox/tree/main/docs/AgentSkills/anthropics/skills/skills/doc-coauthoring
Command: npx skills add https://github.com/pchemguy/AISandbox --skill doc-coauthoring-pchemguy

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 AI reader (sub-agent or new conversation) 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 stakeholder context, drafts each section through brainstorming and curation, then tests the doc with a fresh reader to verify it stands on its own. ## 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 with AI assistance?▼

Use a structured co-authoring workflow that gathers context first, then drafts the spec section by section through brainstorming and curation. Finish by testing the document with a fresh AI reader to catch unclear passages before sharing it.

How do I write a decision doc or RFC collaboratively?▼

Start by dumping all relevant context including alternatives considered and stakeholder concerns. Then build each section iteratively, starting with the core proposal, and validate the final doc by having a context-free reader answer likely questions.

What is reader testing for documents?▼

Reader testing validates a document by having a fresh AI instance with no prior context answer questions readers would ask. It reveals blind spots, assumed knowledge, and contradictions that authors miss because they already understand the material.

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

Yes, if integrations or MCP connectors are available, the workflow can pull context directly from messaging channels and shared documents. Without connectors, you can paste relevant content manually into the conversation.

When should I skip the structured doc workflow?▼

Skip it for short or informal writing where three stages of iteration add unnecessary overhead. The workflow is designed for substantial documents like specs and proposals where reader clarity matters; freeform drafting works fine for quick notes.