doc-coauthoring

Guide co-authors through a three-stage documentation workflow with gap tracking.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/paradox123/shared-ai-docs --skill doc-coauthoring-paradox123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/paradox123/shared-ai-docs/tree/main/skills-repo/skills/doc-coauthoring
Command: npx skills add https://github.com/paradox123/shared-ai-docs --skill doc-coauthoring-paradox123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative documentation often suffers from misalignment, missing gaps, and inconsistent structure. This skill provides a structured, stage-based workflow to guide teams through co-authoring technical docs, proposals, specs, and RFCs with explicit markers for unresolved questions and a clear path from context gathering to reader testing.

Core Features & Use Cases

  • Stage-based workflow including Context Gathering, Refinement & Structure, and Reader Testing to coordinate authors and reviewers.
  • Guardrails and boundaries: Spec vs Plan decisions, DoR/DoD gates, and a Marker System to surface blockers and decisions.
  • History tracking and session management to capture decisions, scope, and changes over time.
  • Flexible handoffs between planning and delivery workflows (e.g., refine-plan, spec-change-delivery) to accommodate different delivery styles.

Quick Start

Start with Stage 1: Context Gathering to collect context, then proceed to 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
What is the best way to co-author technical specs and track unresolved gaps?

A structured co-authoring workflow uses a three-stage process of Context Gathering, Refinement & Structure, and Reader Testing to coordinate authors, apply DoR/DoD gates, and track explicit markers for unresolved questions.

How do I manage an RFC workflow with multiple authors and reviewers?

You can manage an RFC workflow by applying a stage-based process with history tracking and session management to capture decisions, coordinate reviewers, and apply Definition of Ready and Definition of Done gates before finalizing documentation.

Can I use this structured documentation workflow for both planning and delivery?

Yes, you can use this structured documentation workflow for both planning and delivery through flexible handoffs to refine-plan or spec-change-delivery workflows, accommodating different delivery styles while maintaining scope and decision history.

How does a marker system work for collaborative documentation?

A marker system works in collaborative documentation by explicitly flagging unresolved questions and blockers during the Refinement & Structure stage, ensuring gaps are surfaced and tracked until they are resolved through team decisions.

When do I need Definition of Ready and Definition of Done gates for proposals?

You need Definition of Ready and Definition of Done gates for proposals when you want to enforce quality boundaries, ensure structured alignment before refinement, and validate that all documentation gaps are resolved during reader testing.