doc-coauthoring

Orchestrate structured documentation co-authoring with context gathering, refinement, and reader testing.

Updated Oct 22, 2025
One-click install
npx skills add https://github.com/lemu/sea-prototype-template --skill doc-coauthoring-lemu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/lemu/sea-prototype-template/tree/main/.agents/skills/doc-coauthoring
Command: npx skills add https://github.com/lemu/sea-prototype-template --skill doc-coauthoring-lemu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow addresses the challenge of producing clear, well-structured documentation by coordinating multi-person input, iterative refinement, and reader validation.

Core Features & Use Cases

  • Structured three-stage process (Context Gathering, Refinement & Structure, Reader Testing) to synchronize teams across documentation projects.
  • Facilitates drafting of docs, proposals, technical specs, decision records, and other structured content.
  • Includes guided stages, artifact management, and built-in review loops to catch gaps before publishing.

Quick Start

Initiate the three-stage workflow with Context Gathering, Refinement & Structure, and Reader Testing to guide the user from context to reader validation.

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?

Structured co-authoring coordinates multi-person input through Context Gathering, Refinement & Structure, and Reader Testing to synchronize teams on documentation projects. It guides collaborative drafting of technical specs and proposals with built-in review loops to catch gaps before publishing.

How do I coordinate multi-person input for technical specs and proposals?

Coordinate multi-person input by initiating a three-stage workflow: Context Gathering to collect requirements, Refinement & Structure for collaborative drafting, and Reader Testing to validate clarity. Stage-based questioning and artifact management synchronize team contributions.

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

Yes, the co-authoring workflow supports drafting decision records, technical specs, proposals, and structured documentation. Its iterative refinement process applies stage-based questioning and reader validation to ensure clarity across various structured content formats.

What's the best way to validate documentation clarity before publishing?

Reader Testing validates documentation clarity by simulating the audience experience through guided review loops. This final stage of the co-authoring workflow catches structural gaps and verifies that the content effectively communicates its intended message before publishing.

Does structured documentation collaboration require any specific frameworks or dependencies?

No, structured documentation collaboration requires no specific frameworks or external dependencies. The workflow operates independently through its internal three-stage process of Context Gathering, Refinement & Structure, and Reader Testing to guide teams from context to validation.

When should I use a structured co-authoring workflow instead of standard document editing?

Use a structured co-authoring workflow when producing complex documentation requiring multi-person input and iterative refinement. It is ideal for technical specs, proposals, and decision records where built-in review loops and reader validation are essential to catch gaps before publishing.