doc-coauthor

Guide teams through a three-stage documentation co-authoring workflow.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mia-cx/.agents --skill doc-coauthor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthor
Source: https://github.com/mia-cx/.agents/tree/main/skills/doc-coauthor
Command: npx skills add https://github.com/mia-cx/.agents --skill doc-coauthor

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This Doc Co-Authoring Workflow helps users create high-quality documentation by guiding them through three stages: Context Gathering, Refinement & Structure, and Reader Testing, ensuring context is captured, content is refined, and readers are validated.

## Core Features & Use Cases

  • Stage-based guidance for each phase (Context Gathering, Refinement & Structure, Reader Testing) to structure collaborative writing.
  • Triggered when users intend to produce documentation, proposals, technical specs, decision docs, or other structured content.
  • Supports interactive information gathering, iterative drafting, and reader-focused validation, with optional artifact scaffolding.

### Quick Start Begin Stage 1 by offering the three-stage workflow and asking for the user's context and goals.

Frequently Asked Questions about doc-coauthor

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

FAQPage Schema
What is structured document co-authoring and when do I need it?

Structured document co-authoring guides teams through Context Gathering, Refinement & Structure, and Reader Testing. It is needed for technical specs, proposals, design docs, and decision records to ensure context is captured and readers are validated.

How do I start writing a technical spec using a stage-based workflow?

Begin Stage 1 of the technical spec workflow by providing your context and goals. The co-authoring process then moves to Refinement & Structure for iterative drafting, followed by Reader Testing to validate the final artifact.

Can I use this workflow for collaborative proposal writing and decision records?

Yes, the collaborative writing workflow supports proposals and decision records. It triggers when producing structured content, guiding your team through interactive information gathering and iterative drafting across all supported documentation types.

What is the best way to validate technical documentation with readers?

Reader testing validates technical documentation by enforcing a staged process where readers check the refined content. This ensures the structured design docs or proposals are tested against actual reader comprehension before finalizing.

Does this co-authoring workflow support iterative drafting and artifact scaffolding?

Yes, the co-authoring workflow supports iterative drafting and optional artifact scaffolding. During the Refinement & Structure stage, you can iteratively draft content while the system scaffolds necessary artifacts and integrations as needed.