skills.rest
gotar
gotarCOMMUNITY
Explore all skills by this author →
Website𝕏@oskarszrajerGitHub

doc-coauthoring

Guide structured co-authoring of technical specs, proposals, PRDs, and decision docs.

26|1|Updated Jan 6, 2026
Search Tags:#workflow#documentation#iteration#context gathering#co-authoring#reader testing
One-click install
npx skills add https://github.com/gotar/opencode-config --skill doc-coauthoring-gotar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/gotar/opencode-config/tree/main/skills/doc-coauthoring
Command: npx skills add https://github.com/gotar/opencode-config --skill doc-coauthoring-gotar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, collaborative workflow to create documentation efficiently, reducing back-and-forth and ensuring readers can understand and adopt the material.

Core Features & Use Cases

  • Structured Stages: Context Gathering, Refinement & Structure, and Reader Testing guide the entire drafting process.
  • Iterative Drafting: Build sections collaboratively with clarifying questions, multiple options, and surgical edits.
  • Reader Validation: Validate drafts with a fresh perspective to surface gaps before release.
  • Use Cases: Proposals, technical specs, design docs, decision records, and standard documentation tasks.

Quick Start

Start by declaring you want to co-author a document and provide initial context (doc type, audience, and constraints). Then proceed through Stage 1: Context Gathering, Stage 2: Refinement & Structure, and Stage 3: Reader Testing.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I co-author technical specs and proposals with AI?▼

Structured co-authoring uses a three-stage workflow to gather context, refine structure, and run reader testing on proposals and technical specs, reducing back-and-forth and ensuring reader comprehension.

What is the best way to structure collaborative drafting for a PRD?▼

Iterative collaborative drafting builds PRD sections step-by-step using clarifying questions, multiple structural options, and surgical edits to align with constraints and audience needs.

How do I validate documentation gaps before releasing a decision record?▼

Validate decision records by running reader testing, which reviews the draft from a fresh perspective to surface comprehension gaps and ensure readers can adopt the material before release.

Can I use this co-authoring workflow for standard documentation tasks?▼

Yes, this co-authoring workflow supports standard documentation tasks like design docs and decision records once you declare the document type, target audience, and constraints to start context gathering.

Why does collaborative documentation require multiple drafting stages?▼

Collaborative documentation requires multiple stages to separate context gathering, structural refinement, and reader validation, ensuring the final draft satisfies reader comprehension needs and minimizes back-and-forth.

Related Skills

Explore More Content & Communication Skills→
ProjectEuropaProjectEuropa
4

doc-coauthoring

Orchestrate staged AI-assisted documentation workflows from context gathering to reader testing.

Community
Advanced
lemulemu

doc-coauthoring

Orchestrate structured documentation co-authoring with context gathering, refinement, and reader testing.

Community
Advanced
dawsonblockdawsonblock

doc-coauthoring

Manage collaborative document editing with version control, comment resolution, and merge strategies.

Community
Intermediate
Ameen-AlamAmeen-Alam
1

doc-coauthoring

Guide collaborative documentation through context gathering, refinement, and reader testing.

Community
Basic