doc-coauthoring

Guides collaborative document creation through context gathering, iterative drafting, and reader testing.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/wolfmanstout/agent-skills --skill doc-coauthoring-wolfmanstout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/wolfmanstout/agent-skills/tree/main/subtrees/skills/skills/doc-coauthoring
Command: npx skills add https://github.com/wolfmanstout/agent-skills --skill doc-coauthoring-wolfmanstout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and specs alone often produces documents full of blind spots, missing context, and unclear sections that confuse readers. This Skill provides a structured three-stage workflow for co-authoring documents with an AI, ensuring the final doc actually works for its intended audience. ## Core Features & Use Cases - Context Gathering: Collects background, constraints, and organizational context through targeted questions and info dumps before any drafting begins. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates them with the user, then drafts and iteratively refines each section using surgical edits. - Reader Testing: Validates the finished document with a fresh, context-free reader (via sub-agents or a manual fresh conversation) to catch ambiguities, false assumptions, and contradictions. - Use Case: A product manager needs to write a decision doc for a migration plan. The Skill gathers stakeholder context, drafts each section through brainstorming and curation, then tests whether a fresh reader can correctly answer likely questions about the doc. ## Quick Start Ask the assistant to guide you through the doc co-authoring workflow to draft a technical design doc for your upcoming project.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I write a design doc or technical spec with an AI assistant?

Use a structured co-authoring workflow: first dump all project context while the assistant asks clarifying questions, then build the doc section by section through brainstorming and curation, and finally test the draft with a fresh reader to catch blind spots.

How to test whether my document is clear to readers?

Reader testing validates clarity by having a fresh AI instance with no prior context answer realistic reader questions about the document. Questions it answers incorrectly or finds ambiguous reveal gaps to fix before sharing the doc.

What types of documents does this workflow support?

The workflow supports documentation, proposals, technical specs, decision docs, PRDs, RFCs, and similar structured content. It adapts section suggestions based on the document type and any template the user provides.

Can I use this workflow without artifacts or sub-agents?

Yes. Without artifact access, the workflow drafts into a markdown file in the working directory. Without sub-agents, the user manually tests the doc by pasting it into a fresh conversation and asking the generated reader questions.

When should I skip the structured workflow and write freeform?

Freeform writing suits short or low-stakes documents where structured iteration adds overhead. The workflow explicitly offers a freeform option at the start and lets users skip stages whenever they prefer speed over rigor.