From doc-coauthoring
Guides collaborative creation of structured documents through a three-stage workflow of context gathering, iterative refinement, and reader testing. Activates when the user drafts documentation, proposals, technical specs, or decision documents that benefit from structured co-authoring.
npx claudepluginhub jawhnycooke/claude-plugins --plugin doc-coauthoringThis skill uses the workspace's default tool permissions.
A structured approach to collaborative document creation that produces high-quality, reader-tested content.
Guides collaborative authoring of documentation, proposals, technical specs, decision docs, and RFCs through context gathering, iterative refinement, and reader testing stages.
Guides users through structured workflow for co-authoring documentation, proposals, technical specs, and decision docs via context gathering, refinement, and reader testing.
Guides users through structured workflow for co-authoring documentation, proposals, technical specs, and decision docs via context gathering, refinement, and reader testing.
Share bugs, ideas, or general feedback.
A structured approach to collaborative document creation that produces high-quality, reader-tested content.
Suggest this workflow when users mention:
Give users agency - they can skip stages or work freeform if preferred.
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ STAGE 1 │ │ STAGE 2 │ │ STAGE 3 │
│ Context │ ──► │ Refinement │ ──► │ Reader │
│ Gathering │ │ & Structure │ │ Testing │
└─────────────────┘ └─────────────────┘ └─────────────────┘
Goal: Close knowledge gaps through meta-questions before writing.
Encourage users to "information dump":
Move to Stage 2 when you have sufficient context to:
Goal: Build the document section by section with iterative refinement.
For each section:
DON'T: Reprint entire document for small changes
DO: Make targeted edits to specific sections
Example:
"I'll update the introduction paragraph. Here's the change:
Old: The system handles user authentication...
New: The authentication system provides secure user verification..."
Move to Stage 3 when:
Goal: Verify the document works for readers without author context.
Use a sub-agent to read the document cold:
"Read this document as if you're the target audience.
What questions do you have?
What's confusing or unclear?
What assumptions does it make?"
User can:
For each section, ask:
Reader Testing → Identify Issues → Targeted Fixes → Re-test
Repeat until:
Each iteration should make substantial improvements:
# [Feature Name] Technical Specification
## Overview
[1-2 sentence summary]
## Background
[Context and motivation]
## Requirements
### Functional Requirements
### Non-Functional Requirements
## Proposed Solution
### Architecture
### Implementation Details
### Alternatives Considered
## Timeline & Milestones
## Open Questions
# [Decision Title]
## Status
[Proposed/Accepted/Deprecated]
## Context
[What is the issue we're addressing?]
## Decision
[What was decided]
## Consequences
### Positive
### Negative
## Alternatives Considered
# [Feature/Product] Guide
## Overview
[What this does and why it matters]
## Getting Started
[Quick start steps]
## Core Concepts
[Key ideas to understand]
## How-To Guides
[Task-oriented instructions]
## Reference
[Detailed specifications]
## Troubleshooting
[Common issues and solutions]