doc-coauthoring

Coordinate structured co-authoring workflows for documents through staged context gathering, refinement, and reader testing.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Division6066/tempo-rhythm --skill doc-coauthoring-division6066
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/Division6066/tempo-rhythm/tree/main/.agents/skills/doc-coauthoring
Command: npx skills add https://github.com/Division6066/tempo-rhythm --skill doc-coauthoring-division6066

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative document creation often drifts—contexts, goals, and sections become misaligned as multiple authors iterate. This skill provides a structured workflow to capture context, drive iteration, and ensure readers can understand the final document.

Core Features & Use Cases

  • Context Gathering: collect relevant background, stakeholders, and constraints before writing.
  • Refinement & Structure: build sections iteratively with explicit choices, questions, and edits.
  • Reader Testing: validate the document with a fresh perspective to surface gaps.

Quick Start

Start by outlining the document goal and audience, then proceed through Stage 1, Stage 2, and Stage 3 in sequence.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I structure collaborative writing for a technical spec to prevent misalignment?

Structured co-authoring prevents misalignment by enforcing a stage-based workflow: Context Gathering, Refinement & Structure, and Reader Testing. This ensures multiple stakeholders capture goals and constraints before iteratively building sections, resulting in clear, aligned technical specs.

What is the best way to gather context before writing a proposal with multiple stakeholders?

The best way to gather context for a proposal is using a structured workflow that explicitly collects relevant background, stakeholder perspectives, and constraints before writing begins. This initial scaffolding ensures all collaborators share a unified understanding of the document's goals.

How do you validate a PRD with a fresh perspective to surface gaps?

You validate a PRD by applying a Reader Testing stage, which reviews the finalized document from a fresh perspective. This process surfaces structural gaps and unclear sections, ensuring the iterative refinement process yields a document that readers can easily understand.

Can I use this co-authoring workflow for iterative decision docs?

Yes, this co-authoring workflow supports iterative decision docs by applying explicit questions, artifact scaffolding, and structured choices during the Refinement & Structure stage. This accommodates multiple stakeholders and drives formal content toward clarity and reader satisfaction.

When do I need a stage-based documentation workflow instead of standard collaborative editing?

You need a stage-based documentation workflow when collaborative creation drifts due to multiple authors iterating. If contexts, goals, and sections become misaligned in your formal content, enforcing structured stages ensures reader satisfaction and prevents document fragmentation.

How do I start a structured co-authoring workflow for a formal document?

To start structured co-authoring, outline the document goal and audience first. Then proceed sequentially through Context Gathering, Refinement & Structure, and Reader Testing stages, using artifact scaffolding and explicit questions to guide the collaborative writing process.