doc-coauthoring

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps teams write documentation, proposals, technical specs, decision docs, and similar structured content by transferring context, refining content through iteration, and verifying readability for readers.

Core Features & Use Cases

  • Stage-based guidance: Context Gathering, Refinement & Structure, and Reader Testing guide the entire process.
  • Active collaboration: the AI assistant orchestrates the drafting, iteration, and validation steps, keeping stakeholders aligned.
  • Use cases: when starting a new doc, updating a design decision record, or drafting a technical spec, this workflow provides a repeatable framework.

Quick Start

Offer the three-stage co-authoring workflow when the user initiates a doc task and guide them through context gathering, refinement, 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 co-authoring workflow for technical documentation?

A structured co-authoring workflow guides teams through three stages—Context Gathering, Refinement & Structure, and Reader Testing—to collaboratively write technical specs and decision docs with verified readability.

How do I co-author technical specs and proposals with an AI assistant?

You co-author technical specs by following a three-stage workflow: the AI assistant prompts you for context, orchestrates iterative refinement of the structure, and validates the draft through reader testing before finalizing.

When should I use a structured workflow for writing documentation?

Use a structured workflow for writing documentation when starting a new doc, updating a design decision record, or drafting a technical spec. It provides a repeatable framework that keeps stakeholders aligned through context gathering and refinement.

Can I use this co-authoring workflow for updating design decision records?

Yes, you can use this co-authoring workflow for updating design decision records. It explicitly supports drafting and refining decision docs through a built-in transition protocol that moves drafts to final documents.

What's the best way to validate readability before finalizing a proposal?

The best way to validate readability is through the Reader Testing stage. This built-in protocol verifies the draft's clarity for readers and ensures stakeholders are aligned before executing the transition to the final document.

Does this documentation workflow require any specific frameworks or dependencies?

No, this documentation workflow requires no specific frameworks or dependencies. It operates as a standalone stage-based guidance system, using explicit prompts to transfer context and refine content without external environment setup.