doc-coauthoring

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing documentation, specs, and proposals alone often produces documents that make sense to the author but confuse readers, because the author's context never makes it onto the page. This Skill structures the co-authoring process so context is transferred, sections are refined iteratively, and blind spots are caught before publication. ## Core Features & Use Cases - Three-Stage Workflow: Context Gathering (info dumps and clarifying questions), Refinement & Structure (section-by-section brainstorming, curation, and drafting), and Reader Testing (validating the doc with a fresh, context-free reader). - Document Templates: Includes ready-made templates for technical specifications, decision documents (ADRs), PRDs, and RFCs in the references directory. - Reader Testing Prompts: Provides discovery, comprehension, ambiguity, and consistency-check prompts to verify the document works for its intended audience. - Use Case: A product manager needs to write a decision doc comparing two architectural approaches. The Skill gathers stakeholder context, brainstorms options per section, drafts the doc iteratively, then tests it with a fresh reader to catch unexplained assumptions before sharing with the team. ## Quick Start Ask the assistant to guide you through co-authoring a decision document for an upcoming technical choice, starting with a context dump about the problem and constraints.

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 specification with an AI assistant?▼

Use a structured co-authoring workflow: first dump all project context and answer clarifying questions, then build the spec section by section through brainstorming and drafting, and finally test the finished spec with a fresh reader to catch unclear passages.

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

Test the document with a fresh reader that has no prior conversation context. Ask it discovery, comprehension, and actionability questions, plus ambiguity and assumption checks, then fix any gaps it surfaces before publishing.

What document templates are included for decision docs and PRDs?▼

The references directory includes templates for technical specifications, decision documents (ADRs), product requirements documents (PRDs), and RFCs, each with standard sections like status, context, options analysis, requirements, and open questions.

Can I skip stages of the co-authoring workflow?▼

Yes, the workflow is flexible. If you prefer to write freeform or skip a stage, you can decline the structured process at the start or ask to move faster, and the assistant will adjust to your preferred working style.

Why does my document confuse readers even though it seems clear to me?▼

This is the curse of knowledge: authors omit context they take for granted. Reader testing with a context-free reviewer exposes undefined terms, missing rationale, and assumed background knowledge so you can fix them before sharing.