doc-coauthoring

Guide collaborative document creation through a three-stage co-authoring workflow.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Blake-John/agent-config --skill doc-coauthoring-blake-john
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/Blake-John/agent-config/tree/main/.zeroclaw/workspace/skills/doc-coauthoring
Command: npx skills add https://github.com/Blake-John/agent-config --skill doc-coauthoring-blake-john

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Doc co-authoring workflow provides a structured approach to creating documentation, helping teams transfer context, refine content, and validate readability before publication.

Core Features & Use Cases

  • Structured three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing.
  • Interactive guidance with clarifying questions and iterative drafting prompts.
  • Reader testing to catch reader gaps by simulating a fresh reader perspective.

Quick Start

Offer the three-stage co-authoring workflow to the user and begin with Stage 1 if they accept.

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 streamlines collaborative document creation by enforcing a three-stage process: Context Gathering, Refinement & Structure, and Reader Testing. It guides teams to transfer context, refine content, and validate readability before publication.

How do I write technical specs and proposals collaboratively?

To write technical specs and proposals collaboratively, use a staged drafting process with clarifying questions, iterative placeholders, and targeted edits. This structured approach refines content and validates readability using a fresh reader perspective.

Does the co-authoring workflow support reader testing for decision docs?

Yes, the co-authoring workflow supports reader testing for decision docs by simulating a fresh reader perspective. This optional stage catches reader gaps and validates the readability of your structured content before publication.

What is the best way to structure context gathering for technical documentation?

The best way to structure context gathering for technical documentation is using an interactive guided workflow with clarifying questions. This stage transfers project context effectively before moving into refinement and structure drafting.

Can I use iterative drafting with placeholders for collaborative proposals?

Yes, you can use iterative drafting with placeholders for collaborative proposals. The workflow enforces targeted edits and structured refinement, ensuring all team context is integrated before finalizing the document structure.

When should I use a structured workflow for document collaboration?

You should use a structured workflow for document collaboration when drafting technical specs, proposals, or decision docs. It prevents reader gaps by enforcing context gathering, iterative refinement, and readability validation before publication.