doc-coauthoring

name	doc-coauthoring
description	Collaboratively write documents, proposals, specs, PRDs, technical docs, and other written content. Use when user mentions writing docs, proposals, specs, technical specifications, product requirement documents, reports, or any structured written content that benefits from a collaborative co-authoring process.

Doc Co-Authoring Workflow

Guide users through collaborative document creation in three structured stages.

Stage 1: Context Gathering

Collect background information through meta-questions:

• Document type: What kind of document? (proposal, spec, report, PRD, etc.)
• Audience: Who will read this? What's their context?
• Desired impact: What should the reader think/do/feel after reading?
• Raw context: Invite the user to "dump all the context they have" — stream-of-consciousness sharing, channel references, linked documents

After the dump, ask targeted clarifying questions to close knowledge gaps.

Stage 2: Refinement & Structure

Build the document section-by-section using this process:

1. Clarifying questions — what do we need to know for this section?
2. Options brainstorm — generate 5-20 options for key choices
3. Curation — together select the best options
4. Gap check — what's missing or unclear?
5. Draft — write the section content
6. Iterate — revise based on feedback

Being specific in feedback helps learning for subsequent sections.

Stage 3: Reader Testing

Test the completed document with a fresh perspective:

1. Predict reader questions — what will a new reader ask?
2. Run questions against the document — can it answer them?
3. Fix gaps — address anything that isn't clear
4. Simulate paste-in test — imagine a reader pasting the doc into Claude without context. Does it still work?

Key Principle

Quality over speed. Each iteration should yield meaningful improvements. The final document must work for external readers who have none of the context you have.

Document Templates

Proposal Structure

# [Title]
## Executive Summary (1-2 sentences)
## Problem Statement
## Proposed Solution
## Implementation Plan
## Success Metrics
## Risks & Mitigations

Technical Spec Structure

# [Feature Name] - Technical Specification
## Overview
## Goals & Non-Goals
## Design
## API/Interface
## Implementation Details
## Testing Strategy
## Open Questions

PRD Structure

# [Product Feature] - PRD
## Problem
## Solution
## User Stories
## Requirements (Must/Should/Could)
## Success Metrics
## Launch Criteria

Tips for Better Co-Authoring

• Share raw notes, not just polished thoughts
• Reference existing documents or examples you admire
• Specify the tone (formal, casual, technical, etc.)
• Be explicit about length constraints
• Flag sections where you have strong opinions vs. open questions