skills.rest
hotung1027
hotung1027COMMUNITY
Explore all skills by this author →
GitHub

doc-coauthoring

Guide structured three-stage co-authoring workflows for documentation.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/hotung1027/dev.conf --skill doc-coauthoring-hotung1027
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/hotung1027/dev.conf/tree/main/agents/skills/doc-coauthoring
Command: npx skills add https://github.com/hotung1027/dev.conf --skill doc-coauthoring-hotung1027

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through a structured, collaborative workflow to create documentation, proposals, technical specs, decision records, and other structured content, reducing back-and-forth and ensuring clarity.

Core Features & Use Cases

  • Three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing to align context, structure, and reader comprehension.
  • Active coaching: Acts as an active guide, prompting clarifying questions and iterative drafting.
  • Artifact-driven collaboration: Uses staged drafting and optional reader testing to validate the document with a fresh reader.

Quick Start

Start by offering the co-authoring workflow when the user requests to write docs. Then proceed to Stage 1: Context Gathering, asking the initial meta-context questions and inviting a free-form context dump. For example, a user can begin by saying: "I want to draft a design doc."

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 design docs with AI?▼

To co-author technical specs, this Skill guides you through a three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. It prompts clarifying questions and iteratively drafts sections to ensure your design docs are clear and well-structured.

What is the best way to structure an RFC before publishing?▼

The best way to structure an RFC is using a guided workflow that tests readability with a fresh reader. This Skill refines your initial context dump into structured sections and validates reader comprehension to catch gaps before you publish.

Can I use this to draft decision records from a free-form context dump?▼

Yes, you can draft decision records from a free-form context dump. The Context Gathering stage invites you to paste raw ideas, then actively coaches you through structuring those notes into a coherent decision record.

How does the reader testing stage work for proposal writing?▼

Reader testing for proposal writing works by simulating a fresh reader reviewing your drafted sections. This stage validates readability and comprehension, identifying gaps or unclear logic before you finalize and publish the document.

Do I need any specific tools or dependencies to start drafting documents?▼

No specific tools or dependencies are required to start drafting documents. You simply begin by requesting the co-authoring workflow, answering initial meta-context questions, and providing your raw ideas for the document.

Related Skills

Codcyber101Codcyber101

doc-coauthoring

Guide structured co-authoring workflows for documentation, proposals, and technical specs.

Community
Basic
emptistemptist

documentation-and-adrs

Create, store, and reference Architectural Decision Records and technical documentation.

Community
Advanced
garethdainegarethdaine

notion-meeting-intelligence

Gather Notion context and draft meeting agendas with AI research.

Community
Intermediate
Derek-X-WangDerek-X-Wang

doc-coauthoring

Guide documentation through context gathering, refinement, and reader testing.

Community
Advanced