doc-coauthoring

Guide teams through a three-stage co-authoring workflow for documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fragmented and inconsistent documentation workflows slow teams, increase back-and-forth, and weaken the clarity of the final output. This Skill provides a structured, multi-stage approach to co-authoring documentation, enabling teams to transfer context efficiently, iterate content effectively, and verify readability before publication.

Core Features & Use Cases

  • Structured three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing.
  • Stage-specific prompts and clarifying questions to elicit essential information early.
  • Iterative drafting with placeholders, explicit feedback, and surgical edits to converge on a high-quality document.
  • Reader testing guidance to surface ambiguities and ensure the doc reads well for external readers.
  • Template-agnostic guidance that adapts to technical specs, proposals, decision docs, or general documentation.

Quick Start

Start Stage 1 by asking the user about the document type, audience, and desired impact, then guide them through context gathering.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
What is a structured co-authoring workflow for collaborative documentation?▼

It solves fragmented documentation workflows by using a three-stage process: context gathering, refinement with surgical edits, and reader testing to ensure clarity and reduce back-and-forth.

How do I start the collaborative writing process for a technical spec?▼

Start by defining the document type, target audience, and desired impact, then gather essential context through stage-specific prompts before drafting the technical spec.

Can I use this co-authoring process for decision records and proposals?▼

Yes, the template-agnostic guidance adapts to various formats including decision records, proposals, and technical specs, applying the same three-stage workflow to ensure readability.

What is the best way to refine a collaborative draft without losing context?▼

The best way to refine a collaborative draft is through iterative drafting with placeholders and surgical edits based on explicit feedback, ensuring all decisions remain traceable.

How does reader testing improve editorial workflow?▼

Reader testing surfaces ambiguities and verifies that the document reads well for external audiences, ensuring the final output is clear and effective before publication.

Do I need specific templates to use this documentation workflow?▼

No, the workflow provides template-agnostic guidance, meaning it adapts to technical specs, proposals, and general documentation without requiring specific pre-defined templates.