doc-coauthoring

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

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

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 that turns document writing into a guided collaboration, ensuring the final doc actually works for its intended audience. ## Core Features & Use Cases - Context Gathering: Collects background, audience, 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 content with the user, drafts, and iterates through surgical edits until each section is complete. - Reader Testing: Validates the finished document with a fresh, context-free reviewer to catch ambiguities, false assumptions, and contradictions before real readers see it. - Use Case: A product manager needs to write a decision doc for a migration proposal. The workflow gathers stakeholder context, drafts each section iteratively, then tests whether a fresh reader can correctly answer questions about the proposal. ## Quick Start Ask the assistant to guide you through writing a decision doc using the structured co-authoring workflow.

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 decision doc with AI assistance?▼

Use a structured co-authoring workflow that gathers context first, then drafts the document section by section through brainstorming and curation. Finish by testing the doc with a fresh reviewer to catch blind spots before sharing it with stakeholders.

How to structure a technical spec or proposal document?▼

Start by defining the document type, audience, and desired impact, then agree on 3-5 sections appropriate for the doc type. Draft the section with the most unknowns first, leaving summary sections for last.

What is reader testing for documentation?▼

Reader testing validates a document by having a fresh reviewer with no prior context answer realistic reader questions. It surfaces ambiguities, assumed knowledge, and contradictions that authors cannot see because they already understand the material.

Can this workflow use templates or existing documents?▼

Yes, you can provide a template file or link to an existing shared document at the start. The workflow reads the template structure and current content, then builds the draft within that format.

When should I skip the structured workflow and write freeform?▼

Freeform writing fits short, low-stakes documents or when you already have a complete draft. The structured workflow is most valuable for substantial documents like specs, proposals, and decision docs where reader clarity matters.