document-skills-doc-coauthoring

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

Updated Sep 23, 2026
One-click install
npx skills add https://github.com/ehadziabdic/WAgents --skill document-skills-doc-coauthoring-ehadziabdic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document-skills-doc-coauthoring
Source: https://github.com/ehadziabdic/WAgents/tree/main/opencode/skills/document-skills-doc-coauthoring
Command: npx skills add https://github.com/ehadziabdic/WAgents --skill document-skills-doc-coauthoring-ehadziabdic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and technical specs alone often produces documents that make sense to the author but confuse readers. This Skill provides a structured three-stage workflow that closes context gaps, builds content section by section, and validates the result with a fresh reader before publication. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through targeted questions and info dumps, optionally pulling from connected tools like Slack or Google Drive. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates them with the user, drafts content, and iterates through surgical edits. - Reader Testing: Tests the finished document with a fresh AI instance (or sub-agent) that has no prior context, surfacing ambiguities, false assumptions, and contradictions. - Use Case: A product manager drafting a decision doc uses this workflow to dump project context, iteratively build the proposal and trade-offs sections, then verify a fresh reader can correctly answer stakeholder questions before sharing it with the team. ## Quick Start Ask the assistant to guide you through co-authoring a technical spec or decision doc using the structured three-stage workflow.

Frequently Asked Questions about document-skills-doc-coauthoring

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

FAQPage Schema
How do I write a technical spec 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 curation, and finally test the draft with a fresh AI session to catch confusing passages before sharing.

How to draft a decision doc or RFC collaboratively?▼

Start with the section containing the most unknowns, usually the core proposal. Brainstorm 5-20 candidate points per section, curate them with brief justifications, draft the content, and refine through targeted edits rather than rewriting the whole document.

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

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

What is reader testing for documentation?▼

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

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

Freeform writing suits short or low-stakes documents where reader ambiguity carries little risk. The structured workflow is most valuable for substantial documents like specs, PRDs, and decision docs that multiple stakeholders will rely on.