Doc Coauthoring

# Doc Co-Authoring Workflow

This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.

When to Offer This Workflow

**Trigger conditions:**

- User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up"

- User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC"

- User seems to be starting a substantial writing task

**Initial offer:**

Offer the user a structured workflow for co-authoring the document. Explain the three stages:

1. **Context Gathering**: User provides all relevant context while Claude asks clarifying questions

2. **Refinement & Structure**: Iteratively build each section through brainstorming and editing

3. **Reader Testing**: Test the doc with a fresh Claude (no context) to catch blind spots before others read it

Explain that this approach helps ensure the doc works well when others read it (including when they paste it into Claude). Ask if they want to try this workflow or prefer to work freeform.

If user declines, work freeform. If user accepts, proceed to Stage 1.

Stage 1: Context Gathering

**Goal:** Close the gap between what the user knows and what Claude knows, enabling smart guidance later.

Initial Questions

Start by asking the user for meta-context about the document:

1. What type of document is this? (e.g., technical spec, decision doc, proposal)

2. Who's the primary audience?

3. What's the desired impact when someone reads this?

4. Is there a template or specific format to follow?

5. Any other constraints or context to know?

Inform them they can answer in shorthand or dump information however works best for them.

**If user provides a template or mentions a doc type:**

- Ask if they have a template document to share

- If they provide a link to a shared document, use the appropriate integration to fetch it

- If they provide a file, read it

**If user mentions editing an existing shared document:**

- Use the appropriate integration to read the current state

- Check for images without alt-text

- If images exist without alt-text, explain that when others use Claude to understand the doc, Claude won't be able to see them. Ask if they want alt-text generated. If so, request they paste each image into chat for descriptive alt-text generation.

Info Dumping

Once initial questions are answered, encourage the user to dump all the context they have. Request information such as:

- Background on the project/problem

- Related team discussions or shared documents

- Why alternative solutions aren't being used

- Organizational context (team dynamics, past incidents, politics)

- Timeline pressures or constraints

- Technical architecture or dependencies

- Stakeholder concerns

Advise them not to worry about organizing it - just get it all out. Offer multiple ways to provide context:

- Info dump stream-of-consciousness

- Point to team channels or threads to read

- Link to shared documents

**If integrations are available** (e.g., Slack, Teams, Google Drive, SharePoint, or other MCP servers), mention that these can be used to pull in context directly.

**If no integrations are detected and in Claude.ai or Claude app:** Suggest they can enable connectors in their Claude settings to allow pulling context from messaging apps and document storage directly.

Inform them clarifying questions will be asked once they've done their initial dump.

**During context gathering:**

- If user mentions team channels or shared documents:

- If integrations available: Inform them the content will be read now, then use the appropriate integration

- If integrations not available: Explain lack of access. Suggest they enable connectors in Claude settings, or paste the relevant content directly.

- If user mentions entities/projects that are unknown:

- Ask if connected tools should be searched