doc-coauthoring

Coordinate collaborative documentation creation with a three-stage workflow.

Updated Jan 24, 2026

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

Ready to run

npx skills add https://github.com/marianban/fuzzy-guacamole --skill doc-coauthoring-marianban

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/marianban/fuzzy-guacamole/tree/main/.codex/skills/doc-coauthoring
Command: npx skills add https://github.com/marianban/fuzzy-guacamole --skill doc-coauthoring-marianban

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative documentation often suffers from fragmentation and misalignment. This skill provides a structured workflow to transfer context, iteratively refine content, and verify reader usability, reducing back-and-forth and rework.

Core Features & Use Cases

Structured three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing.
Active guidance for writing documentation, proposals, technical specs, or decision documents.
Built-in checkpoints to ensure readability and alignment with target audiences.

Quick Start

Offer the three-stage co-authoring workflow and guide the user through Stage 1: Context Gathering.

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 without causing fragmentation or misalignment?▼

Co-authoring technical documentation requires a structured workflow with context gathering, iterative refinement, and reader validation to prevent fragmentation. This staged process enforces checkpoints, structured drafting, and reader testing to ensure alignment and reduce rework.

What is the best way to write proposals and technical specs collaboratively?▼

Writing proposals and technical specs collaboratively is best handled through a three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This process actively guides structured drafting and verifies readability for target audiences.

How do I start the collaborative documentation workflow?▼

To start collaborative documentation, you begin with Stage 1: Context Gathering. The workflow guides you through initial questions to transfer context, followed by structured drafting and reader testing checkpoints.

Can I use this co-authoring workflow for decision documents and proposals?▼

You can use this co-authoring workflow for decision documents, proposals, and technical specs. It provides active guidance and built-in checkpoints to verify readability and ensure alignment with your target audiences.

Does collaborative documentation work without reader testing and validation?▼

Collaborative documentation without reader testing often suffers from misalignment and requires rework. Enforcing a staged process with reader validation ensures readability and verifies that the documentation aligns with target audiences.