doc-coauthoring

Guide structured three-stage documentation co-authoring with context gathering, refinement, and reader testing.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/leto-labs/jarvis-template --skill doc-coauthoring-leto-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/leto-labs/jarvis-template/tree/main/.claude/skills/doc-coauthoring
Command: npx skills add https://github.com/leto-labs/jarvis-template --skill doc-coauthoring-leto-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps teams co-author documentation efficiently by capturing context, structuring content, and validating readability.

Core Features & Use Cases

  • Context Gathering: Collect relevant context and questions from stakeholders
  • Refinement & Structure: Iteratively build sections and outlines to ensure coherence
  • Reader Testing: Validate the document with a fresh perspective before publication
  • Use Case: Teams drafting PRDs or design docs can apply this workflow to produce ready-to-read documents

Quick Start

Offer the structured three-stage co-authoring workflow when a user asks to write a document, and begin with Stage 1: 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 co-author technical documentation with my team?

Co-author technical documentation by following a structured three-stage workflow: gather context from stakeholders, iteratively refine structure, and test with readers to validate readability before publication.

What is the best way to structure a collaborative design doc writing process?

Structure collaborative design doc writing using iterative refinement to build sections and outlines, ensuring document coherence and traceable edits before reader testing.

How does reader testing work for technical specs and proposals?

Reader testing for technical specs validates the document with a fresh perspective before publication, ensuring the content is clear and ready-to-read for the intended audience.

Can I use this workflow for drafting PRDs and decision records?

Yes, you can use this workflow for drafting PRDs and decision records, as it applies to writing technical specifications, proposals, and design documents through structured collaboration.

What is context gathering for collaborative documentation?

Context gathering for collaborative documentation collects relevant background and questions from stakeholders to establish a shared foundation before drafting begins.

When do I need a structured workflow for writing documentation?

You need a structured workflow for writing documentation when teams require clear structure, traceable edits, and reader-oriented validation to produce ready-to-read documents efficiently.