doc-coauthoring

Guide staged document creation through context gathering, refinement, and reader testing.

2|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/john-data-chen/hermes-agent-backup --skill doc-coauthoring-john-data-chen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/john-data-chen/hermes-agent-backup/tree/main/skills/doc-coauthoring
Command: npx skills add https://github.com/john-data-chen/hermes-agent-backup --skill doc-coauthoring-john-data-chen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.

Core Features & Use Cases

  • Three-stage workflow guiding Context Gathering, Refinement & Structure, and Reader Testing
  • Triggered when the user mentions writing documentation, proposals, specs, or similar tasks
  • Stage-by-stage guidance with questions, brainstorming, and iterative drafting
  • Optional reader testing step to validate readability with a fresh perspective

Quick Start

Offer the three-stage co-authoring workflow to the user and proceed to Stage 1 upon acceptance

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 benefits from a three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This structured co-authoring approach guides stage-by-stage drafting, brainstorming, and iterative refinement for technical specs, proposals, and decision docs.

What is the stage-gate workflow for co-authoring documentation?

The stage-gate workflow for co-authoring documentation divides the writing process into three distinct stages: Context Gathering, Refinement & Structure, and Reader Testing. Each stage acts as a gate, ensuring frontmatter metadata, artifact management, and reader validation are completed before progressing.

How do I validate readability and structure during iterative drafting?

You validate readability during iterative drafting by applying an optional reader testing step. This stage tests the document with a fresh perspective to ensure the structure is logical and the content is easily understood by the target audience before final artifact management.

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

Yes, this structured co-authoring workflow applies directly to writing decision docs, proposals, and technical specs. It satisfies requirements for staged drafting and frontmatter metadata, making it suitable for any collaborative documentation requiring iteration and reader validation.

Does the documentation co-authoring process require frontmatter metadata?

Yes, the documentation co-authoring process explicitly satisfies requirements for frontmatter metadata and artifact management. This metadata is handled during the Refinement & Structure stage to ensure documents are properly organized and categorized.

What is the best way to manage stage-by-stage guidance for proposal writing?

The best way to manage stage-by-stage guidance for proposal writing is through a structured co-authoring workflow. It provides active guidance through Context Gathering, Refinement & Structure, and Reader Testing, ensuring brainstorming and iterative drafting occur logically.