doc-coauthoring

Guides multi-stage document creation with context gathering, refinement, and reader testing.

10|Updated Jun 3, 2020
One-click install
npx skills add https://github.com/magic3007/dotfiles --skill doc-coauthoring-magic3007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/magic3007/dotfiles/tree/main/claude/project_skills/doc-coauthoring
Command: npx skills add https://github.com/magic3007/dotfiles --skill doc-coauthoring-magic3007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured workflow to guide teams through collaborative document creation, reducing misalignment and revision overhead by standardizing how context is gathered, content is refined, and readers are validated.

Core Features & Use Cases

  • Context Gathering: Collects goals, audience, constraints, and references before drafting.
  • Refinement & Structure: Breaks documents into sections, iterates content with prompts, and aligns on the final structure.
  • Reader Testing: Validates clarity with a fresh perspective to detect gaps and ambiguities.
  • Use Case: A team writing a product requirements document can follow Stage 1 to capture context, Stage 2 to craft sections, and Stage 3 to test reader comprehension.

Quick Start

Describe the document type and provide initial context to start Stage 1 of the co-authoring workflow.

Frequently Asked Questions about doc-coauthoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a structured co-authoring workflow for documentation?

A structured co-authoring workflow standardizes document creation by guiding teams through Context Gathering, Refinement & Structure, and Reader Testing to reduce misalignment and ensure clarity. It enforces a disciplined process with staged questions, drafting, and validation to ensure reader readiness.

How do I write a product requirements document with multiple stakeholders?

To write a product requirements document collaboratively, follow a multi-stage co-authoring workflow: capture goals and audience in Context Gathering, iteratively draft and align on sections during Refinement, and validate reader comprehension during Reader Testing to detect gaps and ambiguities.

Can I use this co-authoring workflow for specs and decision docs?

Yes, you can use this co-authoring workflow for writing tasks like proposals, specs, and decision docs. It standardizes how context is gathered, content is refined, and readers are validated, reducing revision overhead and ensuring consistency across various documentation types.

What's the best way to validate document clarity before sharing with readers?

The best way to validate document clarity is through Reader Testing, which examines the draft from a fresh perspective to detect gaps and ambiguities. This staged validation ensures the final documentation is clear, consistent, and reader-ready before distribution.

How do I start the collaborative document creation process?

To start collaborative document creation, describe the document type and provide initial context such as goals, audience, constraints, and references. This initiates Stage 1 of the workflow, ensuring all necessary context is collected before drafting begins.