doc-coauthoring

Guide collaborative document creation through a three-stage workflow.

1|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/evalops/maestro --skill doc-coauthoring-evalops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/evalops/maestro/tree/main/skills/doc-coauthoring
Command: npx skills add https://github.com/evalops/maestro --skill doc-coauthoring-evalops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide users through a structured, collaborative document creation process. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Core Features & Use Cases

  • Three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing.
  • Trigger conditions: user mentions writing documentation, proposals, design specs, RFCs.
  • Structured guidance: initial offer, stage-by-stage prompts, and artifact scaffolding to support collaborative drafting.
  • Reader testing preparation: enables a fresh-review pass to catch gaps before distribution.

Quick Start

Offer the three-stage co-authoring workflow to guide doc creation, starting 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 specs and proposals through an iterative process?

Co-authoring technical specs and proposals uses a three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This structured process guides collaborative drafting and iterative refinement to produce verified documentation.

What is the best way to structure collaborative documentation creation?

Structured documentation creation applies a stage-based workflow that begins with initial context transfer, moves to content refinement and structure, and ends with a fresh-review reader testing pass to catch gaps before distribution.

Can I use this workflow for drafting RFCs and decision docs?

Yes, the co-authoring workflow supports drafting RFCs, decision docs, technical specs, and proposals. It provides stage-by-stage prompts and artifact scaffolding to guide these specific documentation types from initial context to final review.

How do I prepare documentation for reader testing before distribution?

Reader testing preparation involves a dedicated fresh-review pass at the final stage of the co-authoring workflow. This step catches structural gaps and verifies the document works for its intended audience before final distribution.

Does the structured drafting workflow support file creation for artifacts?

Yes, the structured drafting workflow includes optional create_file usage for artifact scaffolding. This supports the collaborative document creation process by generating necessary files during the Context Gathering and Refinement stages.

When do I need a stage-based workflow for content creation?

A stage-based workflow is needed when creating documentation that requires iterative refinement and reader testing, such as proposals, design specs, or RFCs. It ensures structured guidance from initial context transfer through final verification.