doc-coauthoring

Guide collaborative document creation through a three-stage workflow.

3|Updated Jan 14, 2014
One-click install
npx skills add https://github.com/prateek/dotfiles --skill doc-coauthoring-prateek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/prateek/dotfiles/tree/main/.agents/skills/doc-coauthoring
Command: npx skills add https://github.com/prateek/dotfiles --skill doc-coauthoring-prateek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative document creation can be slow and error-prone without a structured workflow that guides contributors through gathering context, refining structure, and testing clarity.

Core Features & Use Cases

  • Stage-based guidance for Context Gathering, Refinement & Structure, and Reader Testing.
  • Iterative drafting with clear section scaffolding, questions, and options to choose from.
  • built-in processes for artifact handling, versioning, and reviewer feedback to ensure readers can quickly understand the document intent.

Quick Start

Begin Stage 1 by providing the project context and desired document type to kick off the co-authoring workflow.

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 document creation for technical specs and proposals?

Collaborative document creation is structured using a three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This stage-based guidance ensures iterative refinement and high-quality, understandable long-form content.

What is the best way to guide a team through iterative drafting and reviewer feedback?

Iterative drafting is guided through clear section scaffolding, structured questions, and selectable options. This workflow integrates built-in processes for artifact handling, versioning, and reviewer feedback to ensure document intent is quickly understood.

Can I use this workflow for writing design specs and decision records?

Yes, this workflow applies to writing technical docs, proposals, design specs, decision records, and similar long-form content. It provides explicit blockers and milestones specifically for implementation-oriented documents.

How do I start the co-authoring workflow for a new project document?

To start the co-authoring workflow, begin Stage 1 by providing the project context and desired document type. This initial context gathering kicks off the structured refinement and reader testing phases.

When do I need a structured workflow for collaborative documentation?

You need a structured workflow for collaborative documentation when creating long-form content that benefits from iterative refinement and reader testing. It prevents slow, error-prone drafting by applying clear section scaffolding and explicit milestones.