doc-coauthoring

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

Updated Jan 21, 2026

Search Tags:#workflow #documentation #collaboration #coauthoring #reader-testing #documentation-process

Ready to run

npx skills add https://github.com/rafaelramosdf/antigravity-agents --skill doc-coauthoring-rafaelramosdf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/rafaelramosdf/antigravity-agents/tree/main/templates/agent-template-en/skills/doc-coauthoring
Command: npx skills add https://github.com/rafaelramosdf/antigravity-agents --skill doc-coauthoring-rafaelramosdf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured workflow to guide users through collaborative documentation, helping teams move from initial context to a reader-validated document with clear ownership and revision history.

Core Features & Use Cases

Three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing, to coordinate input, drafting, and validation.
Supports writing documentation, proposals, technical specs, or decision docs with iterative feedback and clear handoffs.
Use Case: A team drafts a technical spec and validates it with stakeholders before publishing.

Quick Start

Kick off Stage 1 by gathering context about the document type, audience, and desired impact.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema

How do I co-author technical documentation with multiple stakeholders?▼

Co-authoring technical documentation requires a structured workflow that moves from context gathering to iterative drafting and reader testing, ensuring clear ownership and validated output. This skill coordinates input collection, staged refinement, and stakeholder validation.

What is the best way to structure a collaborative technical spec writing process?▼

The best way to structure a collaborative technical spec writing process is using a staged workflow: context collection, refinement and structure drafting, and reader-focused validation. This approach enables iterative feedback, traceable decisions, and clear handoffs before publishing.

How do I gather context and audience requirements before drafting a proposal?▼

Gathering context and audience requirements for a proposal starts with Stage 1 of the documentation workflow, collecting details about document type, target audience, and desired impact to guide iterative drafting and ensure reader-focused validation.

Can I use this documentation workflow for decision documents and technical specs?▼

Yes, you can use this documentation workflow for decision documents and technical specs. It supports writing various document types by applying a staged process of context collection, iterative drafting, and reader testing to ensure high-quality, validated output.

How does reader testing work in a co-authoring workflow?▼

Reader testing in a co-authoring workflow validates the drafted documentation with stakeholders before publishing. It acts as the final stage to ensure the document achieves its desired impact, enabling iterative refinement based on reader-focused feedback.