doc-coauthoring

Guide structured documentation co-authoring through context gathering, refinement, and reader testing.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ksm0709/dotfiles --skill doc-coauthoring-ksm0709
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/ksm0709/dotfiles/tree/main/opencode/config/skills/doc-coauthoring
Command: npx skills add https://github.com/ksm0709/dotfiles --skill doc-coauthoring-ksm0709

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users through a structured, collaborative workflow for co-authoring documentation. It helps teams transfer context, refine content through iteration, and verify readability and usability of the final document.

Core Features & Use Cases

  • Stage 1: Context Gathering — collect all relevant context via questions, notes, and references to align stakeholders.
  • Stage 2: Refinement & Structure — iteratively draft sections, organize content, and validate coherence across the document.
  • Stage 3: Reader Testing — simulate fresh readership to identify gaps, ambiguities, and assumptions; refine accordingly.
  • Trigger and transition — automatically offer the workflow when users indicate they need to write documentation, proposals, technical specs, or decision docs.
  • Exits and handoffs — provide structured handoffs between stages and clear prompts for the next steps.

Quick Start

Offer the co-authoring workflow when the user requests writing documentation and guide them through Context Gathering, Refinement & Structure, and Reader Testing.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
What is a structured workflow for collaborative documentation writing?

A structured collaborative documentation workflow aligns stakeholders by guiding teams through Context Gathering, Refinement & Structure, and Reader Testing stages to ensure high-quality technical specs and proposals.

How do I start co-authoring technical specs with my team?

Start co-authoring technical specs by initiating Context Gathering to collect relevant notes and references, then iteratively draft sections during Refinement & Structure before validating coherence at the Reader Testing stage.

Can I use this workflow for writing proposals and decision records?

Yes, you can use this workflow for writing proposals and decision records, as it automatically triggers and applies structured templates and checkpoints to maintain clarity across various documentation types.

What's the best way to test if a document is clear for fresh readers?

The best way to test document clarity is through Reader Testing, which simulates fresh readership to identify gaps, ambiguities, and assumptions so you can refine the content accordingly.

How does the workflow transition between documentation stages?

The workflow transitions between stages using structured handoffs and explicit prompts, providing clear checkpoints that guide users from initial context collection directly to the next refinement steps.