doc-coauthoring

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

Updated May 15, 2026
One-click install
npx skills add https://github.com/danielbere1973/promoar --skill doc-coauthoring-danielbere1973
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/danielbere1973/promoar/tree/main/.agents/skills/doc-coauthoring
Command: npx skills add https://github.com/danielbere1973/promoar --skill doc-coauthoring-danielbere1973

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and technical specs alone often leads to blind spots, missing context, and documents that confuse readers. This Skill provides a structured three-stage workflow that helps you transfer context to the AI, build each section iteratively, and verify the document works for real readers before publishing. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through structured questions and info dumps, with support for pulling content from connected tools like Slack or Google Drive. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates content with your feedback, and drafts iteratively using artifacts or markdown files. - Reader Testing: Validates the finished document with a fresh AI instance (or sub-agents) to catch ambiguities, false assumptions, and contradictions before others read it. - Use Case: You need to write a decision doc for a technical migration. The workflow helps you dump all relevant context, draft each section through brainstorming and curation, then test whether a fresh reader can correctly answer questions about your proposal. ## Quick Start Ask the AI to help you write a design doc using the structured co-authoring workflow, starting with 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 write a technical design doc with AI assistance?▼

Use a structured co-authoring workflow: first dump all project context while the AI asks clarifying questions, then build each section through brainstorming and iterative drafting, and finally test the doc with a fresh AI conversation to catch blind spots before sharing it.

What is the best workflow for drafting a decision doc or RFC?▼

A three-stage approach works well: context gathering to close knowledge gaps, section-by-section refinement with brainstorming and curation, and reader testing where a context-free reader answers questions about the doc to reveal ambiguities.

Can this workflow pull context from Slack or Google Docs?▼

Yes, if integrations or MCP connectors are available, the workflow can read team channels, threads, and shared documents directly. Without connectors, you can paste relevant content manually or enable connectors in your AI settings.

How do I test whether my document is clear to readers?▼

Use reader testing: generate 5-10 questions a real reader would ask, then have a fresh AI conversation with no prior context answer them using only the document. Wrong answers or confusion reveal gaps to fix before publishing.

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

Skip the structured workflow for short, low-stakes documents or when you already have a clear draft. The full three-stage process is most valuable for substantial documents like specs, proposals, and decision docs that many stakeholders will read.