Document Co-Authoring
Overview
Structured documents fail when authored in a single monolithic pass without upfront alignment or iterative testing. This skill governs the interactive co-authoring loop between an author and an agent across three formal stages: context gathering, section planning and iterative building, followed by reader testing and decision recording. It focuses entirely on managing the collaborative process and pacing, leaving specific domain conventions and line-level editing to dedicated sibling skills.
When to use
Use this skill when collaborating on substantial multi-section documents requiring careful alignment, such as formal proposals, technical specifications, product requirement documents, design documents, architecture records, and Request for Comments. It ensures shared intent is established before writing begins and maintains rigorous quality gates through iterative section locks.
When NOT to use
Do not use this skill for quick, single-paragraph memos or scratchpad notes where process overhead exceeds value. It is not for producing a standalone first draft without interaction (use ac-drafting), line-editing an existing completed draft (use ac-editing), or establishing domain-specific document conventions (use ac-spec-writing).
Subskill index
| Leaf |
Domain segment |
Scope (one line) |
subskills/when-to-offer.md |
writing/when-to-offer |
Deciding when to offer a structured co-authoring workflow versus freeform generation; gaining author consent before imposing process |
subskills/context-gathering.md |
writing/context-gathering |
Stage 1 context gathering; structured interview covering purpose, reader, decision, venue, constraints, existing material, and success test |
subskills/section-planning.md |
writing/section-planning |
Planning document skeleton as reader questions answered in answer-first order; section ownership, scope boundaries, and author confirmation |
subskills/iterative-building.md |
writing/iterative-building |
Stage 2 iterative building; drafting one section at a time through brainstorm, edit, confirm cycles while preserving author voice and managing disagreements |
subskills/reader-testing.md |
writing/reader-testing |
Stage 3 fresh-reader test; simulating a reader with zero session context to catch jargon, hidden assumptions, and unresolved questions |
subskills/decision-records.md |
writing/decision-records |
Managing the document decision trail; recording chosen options, rejected alternatives, trade-offs, and open questions to preserve institutional rationale |
subskills/session-handoff.md |
writing/session-handoff |
Managing session closure and handoff; recording per-section status, resumption pointers, draft version markers, and author sign-off |
Status and honest limits
Status is seedling. This skill governs the interactive collaboration loop and structural progression of document authoring. It does not automate domain research, perform deep fact-checking of external claims, or replace the author's substantive judgment on strategic business decisions.
1---2name: ac-doc-coauthoring3description: "Staged co-authoring workflow for structured documents (proposals, specs, decision docs, RFCs): the author and the agent build the document together through explicit stages including context gathering, iterative section-by-section construction, and a fresh-reader test before release. Use when asking 'co-author this document', 'draft this proposal with me', 'let's write this spec together', 'guide me through writing this RFC', 'test my draft with a fresh reader', 'PRD', 'decision doc'. Not for producing a first draft alone (ac-drafting), line-editing an existing draft (ac-editing), or doc-type conventions (ac-spec-writing)."4license: MIT5metadata:6 source: https://skillmd.com/skills/jiayaoqijia/ac-doc-coauthoring7 domain: writing8---910# Document Co-Authoring1112## Overview1314Structured documents fail when authored in a single monolithic pass without upfront alignment or iterative testing. This skill governs the interactive co-authoring loop between an author and an agent across three formal stages: context gathering, section planning and iterative building, followed by reader testing and decision recording. It focuses entirely on managing the collaborative process and pacing, leaving specific domain conventions and line-level editing to dedicated sibling skills.1516## When to use1718Use this skill when collaborating on substantial multi-section documents requiring careful alignment, such as formal proposals, technical specifications, product requirement documents, design documents, architecture records, and Request for Comments. It ensures shared intent is established before writing begins and maintains rigorous quality gates through iterative section locks.1920## When NOT to use2122Do not use this skill for quick, single-paragraph memos or scratchpad notes where process overhead exceeds value. It is not for producing a standalone first draft without interaction (use ac-drafting), line-editing an existing completed draft (use ac-editing), or establishing domain-specific document conventions (use ac-spec-writing).2324## Subskill index2526| Leaf | Domain segment | Scope (one line) |27|---|---|---|28| `subskills/when-to-offer.md` | writing/when-to-offer | Deciding when to offer a structured co-authoring workflow versus freeform generation; gaining author consent before imposing process |29| `subskills/context-gathering.md` | writing/context-gathering | Stage 1 context gathering; structured interview covering purpose, reader, decision, venue, constraints, existing material, and success test |30| `subskills/section-planning.md` | writing/section-planning | Planning document skeleton as reader questions answered in answer-first order; section ownership, scope boundaries, and author confirmation |31| `subskills/iterative-building.md` | writing/iterative-building | Stage 2 iterative building; drafting one section at a time through brainstorm, edit, confirm cycles while preserving author voice and managing disagreements |32| `subskills/reader-testing.md` | writing/reader-testing | Stage 3 fresh-reader test; simulating a reader with zero session context to catch jargon, hidden assumptions, and unresolved questions |33| `subskills/decision-records.md` | writing/decision-records | Managing the document decision trail; recording chosen options, rejected alternatives, trade-offs, and open questions to preserve institutional rationale |34| `subskills/session-handoff.md` | writing/session-handoff | Managing session closure and handoff; recording per-section status, resumption pointers, draft version markers, and author sign-off |3536## Status and honest limits3738Status is seedling. This skill governs the interactive collaboration loop and structural progression of document authoring. It does not automate domain research, perform deep fact-checking of external claims, or replace the author's substantive judgment on strategic business decisions.