doc-coauthoring

Guide teams through a three-stage workflow for RawDrive documentation.

Updated Dec 17, 2025
One-click install
npx skills add https://github.com/veerababumanyam/RawDrive102 --skill doc-coauthoring-veerababumanyam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/veerababumanyam/RawDrive102/tree/main/.claude/skills/doc-coauthoring
Command: npx skills add https://github.com/veerababumanyam/RawDrive102 --skill doc-coauthoring-veerababumanyam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams through a structured, three-stage co-authoring workflow to produce consistent, high-quality RawDrive documentation, including specs, ADRs, PRDs, and technical docs.

Core Features & Use Cases

  • Three-stage process: Context Gathering, Refinement & Structure, and Reader Testing.
  • Preset templates and file organization for specs (spec.md, plan.md, tasks.md), ADRs (docs/ADR/.md), and technical specs (docs/TechnicalSpecs/.json).
  • Collaboration-friendly workflows that support multi-person drafting, review cycles, and versioning.

Quick Start

Start by inviting your team to provide context for a new document. Then run through the three stages to produce a ready-to-publish artifact.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I structure technical specs and PRDs for consistent team documentation?

To structure technical specs and PRDs, use a three-stage co-authoring workflow: context gathering, refinement and structure, and reader testing, applying standardized templates for consistent team documentation.

What is the best way to co-author ADRs across a repository?

The best way to co-author ADRs is using a structured workflow that applies standardized templates, supporting multi-person drafting, review cycles, and versioning across your repository's docs directory.

How does the three-stage documentation workflow work?

The three-stage documentation workflow operates by first gathering context from your team, then refining and structuring the document, and finally conducting reader testing to produce ready-to-publish artifacts.

What templates are included for creating specs and technical documents?

Included templates cover file organization for specs using spec.md, plan.md, tasks.md, ADRs using docs/ADR/*.md, and technical specs using docs/TechnicalSpecs/*.json files.

Can I use this co-authoring workflow for multi-person drafting and review cycles?

Yes, you can use this co-authoring workflow for multi-person drafting, as it includes collaboration-friendly workflows that support review cycles and versioning to finalize technical documents.

When do I need a structured workflow for documentation?

You need a structured workflow for documentation when your team requires consistent, high-quality specs, ADRs, PRDs, and technical docs produced through defined context gathering and reader testing stages.