doc-coauthoring

Co-authors documents via a three-stage workflow with YAML frontmatter.

Updated May 25, 2026
One-click install
npx skills add https://github.com/Chieji/my-skills --skill doc-coauthoring-chieji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/Chieji/my-skills/tree/main/doc-coauthoring
Command: npx skills add https://github.com/Chieji/my-skills --skill doc-coauthoring-chieji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users through a structured workflow for co-authoring documentation, helping teams transfer context, refine content through iteration, and verify that docs work for readers.

Core Features & Use Cases

  • Structured three-stage workflow: Context Gathering, Refinement & Structure, Reader Testing
  • Supports writing documentation, proposals, technical specs, decision docs, and similar artifacts
  • Interactive guidance with clarifying questions, iterative drafting, and reader validation

Quick Start

Offer the co-authoring workflow when the user mentions writing documentation or related docs, then guide them through Stage 1: Context Gathering.

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 structure technical documentation co-authoring?

Documentation co-authoring uses a three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This process guides teams from initial context questions through iterative drafting to final reader validation for technical specs and proposals.

How do I write a technical proposal using a structured drafting workflow?

Draft a technical proposal by initiating a structured co-authoring workflow that starts with Context Gathering. You answer clarifying questions to transfer context, refine the content and structure iteratively, and then validate the draft through reader testing to ensure it works for the intended audience.

Can I use this structured drafting workflow for decision docs and technical specs?

Yes, the structured co-authoring workflow applies to writing documentation, proposals, technical specs, and decision docs. It guides you through context gathering, refinement, and reader testing to ensure complex technical content is validated by readers.

How does reader testing work during the documentation refinement process?

Reader testing during documentation refinement validates that the drafted content works for its intended audience. It serves as the final stage in the co-authoring workflow, ensuring the structured context and refined drafts effectively communicate the necessary technical information.

Does the co-authoring workflow require any specific file formats or dependencies?

The co-authoring workflow requires no external dependencies. It enforces a YAML frontmatter structure containing name and description fields, and optionally supports resource directories like scripts, references, and assets to be utilized on demand during the drafting stages.