doc-coauthoring

Guide structured co-authoring workflows for documentation, proposals, and technical specs.

3|Updated Dec 22, 2025

Search Tags:#workflow #documentation #iteration #co-authoring #content-creation #reader-testing

Ready to run

npx skills add https://github.com/JoaquinCampo/codex-skills --skill doc-coauthoring-joaquincampo

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the inefficiency of ad-hoc documentation by guiding users through a structured co-authoring workflow that helps transfer context, refine content through iteration, and verify readability for readers.

Core Features & Use Cases

Context Gathering: Gather all relevant context before drafting, with clarifying questions.
Refinement & Structure: Iteratively build sections through brainstorming and editing.
Reader Testing: Validate the document with a fresh session to catch reader blind spots.

Use cases include writing documentation, proposals, technical specs, decision docs, and other structured content.

Quick Start

Offer the three-stage workflow to the user. If accepted, proceed to Stage 1: Context Gathering and begin with initial questions to elicit meta-context. If declined, you may proceed with freeform drafting.

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 documentation?▼

A structured co-authoring workflow is a repeatable process that guides creating documented content through staged steps: gathering context, refining structure through iterative edits, and reader testing to ensure readability.

How do I co-author technical specs and proposals step by step?▼

To co-author technical specs and proposals, start with context gathering and clarifying questions, then iteratively build sections through brainstorming and drafting, and finally validate the document with a fresh reader testing session.

When do I need a structured workflow for content creation?▼

You need a structured workflow for content creation when ad-hoc documentation becomes inefficient, requiring a repeatable process to transfer context, refine content through iteration, and verify readability for intended readers.

Can I draft decision docs freeform without the staged questions?▼

Yes, you can draft decision docs freeform. The workflow offers a three-stage process, but if you decline the structured context gathering and refinement stages, you can proceed directly with freeform drafting.

How does reader testing catch blind spots in documentation?▼

Reader testing catches blind spots in documentation by validating the drafted content with a fresh session, simulating a new reader's perspective to identify areas where context or structure may be unclear before finalizing.

What is the best way to refine document structure through iteration?▼

The best way to refine document structure through iteration is to build sections progressively via brainstorming and editing, ensuring all relevant context is gathered and refined before moving to the reader testing phase.