doc-coauthoring

Guide users through staged co-authoring workflows for structured documents.

1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/mortenbroesby/playground --skill doc-coauthoring-mortenbroesby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/mortenbroesby/playground/tree/main/.skills/doc-coauthoring
Command: npx skills add https://github.com/mortenbroesby/playground --skill doc-coauthoring-mortenbroesby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow provides a structured, multi-stage approach to co-authoring documentation, helping teams transfer context, refine content through iteration, and verify reader comprehension before publication.

Core Features & Use Cases

  • Structured three-stage process: Context Gathering, Refinement & Structure, and Reader Testing, guiding writers from initial inquiry to final validation.
  • Trigger-based activation: Offer this workflow when users mention writing docs, proposals, specs, decision docs, RFCs, or similar documentation tasks.
  • Interactive Stage 1: Collect all relevant context via clarifying questions and an optional info dump; Stage 2 builds and iterates on the document section by section; Stage 3 tests the draft with a fresh reader to surface gaps.
  • Optional artifacts and scaffolds: Create artifacts or files that provide a working structure with placeholders to accelerate drafting; adapt or skip stages as needed.
  • Supports freeform fallback: If the user declines the structured workflow, proceed with freeform drafting.

Quick Start

Offer the structured co-authoring workflow at the start of a writing task and begin Stage 1 with clarifying questions and an initial context dump.

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 guides teams through a three-stage process: context gathering, iterative refinement, and reader testing to create technical specs, proposals, and RFCs with verified comprehension before publication.

How do I write technical specs and RFCs using a stage-based process?▼

Begin with Stage 1 context gathering via clarifying questions, proceed to Stage 2 for section-by-section refinement and structure, and finish with Stage 3 reader testing to surface gaps in the draft.

Can I draft proposals and decision notes without following a rigid writing process?▼

Yes, if you decline the structured co-authoring workflow, the system supports a freeform fallback mode to proceed with drafting documentation without enforcing the staged process.

Does this documentation workflow provide scaffolding for new drafts?▼

Yes, the workflow optionally creates artifacts and files that provide a working structure with placeholders to accelerate the drafting of technical specs and decision notes.

What is the best way to test if readers understand my documentation before publishing?▼

The best way to verify reader comprehension is using Stage 3 reader testing, which tests the draft with a fresh reader to surface gaps and validate context transfer before final publication.

When should I use a structured writing process instead of freeform drafting?▼

Use a structured writing process for technical documentation, RFCs, and proposals requiring stakeholder feedback and iterative refinement, whereas freeform drafting suits simpler content without reader testing needs.