doc-coauthoring

Guide teams through a three-stage co-authoring workflow for structured documentation.

1.2k|53|Updated Dec 24, 2025

Search Tags:#workflow #documentation #co-authoring #reader-testing #context-gathering #stage-approach

Ready to run

npx skills add https://github.com/polyuiislab/infiAgent --skill doc-coauthoring-polyuiislab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/polyuiislab/infiAgent/tree/main/skills/doc-coauthoring
Command: npx skills add https://github.com/polyuiislab/infiAgent --skill doc-coauthoring-polyuiislab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, stage-based workflow to guide users through collaborative documentation creation. It helps when creating documentation, proposals, technical specs, decision docs, or similar structured content by ensuring clear context gathering, iterative refinement, and reader-oriented validation.

Core Features & Use Cases

Three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing to ensure coherent, reader-friendly docs.
Trigger-based guidance: offers the workflow when users mention writing docs, proposals, specs, RFCs, or related tasks.
Practical deployment: includes guidance on asking clarifying questions, brainstorming options, drafting sections, and iterative refinement; supports using artifacts to scaffold work when available.

Quick Start

Start by opting into the structured co-authoring workflow and proceeding to 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 a structured workflow for collaborative documentation creation?▼

A structured workflow for collaborative documentation creation uses a three-stage process of context gathering, iterative refinement, and reader testing to produce well-structured technical documents, proposals, and decision records.

How do I co-author technical specs and RFCs with a team?▼

You co-author technical specs and RFCs by following a stage-based approach: gathering context and clarifying requirements, drafting and iteratively refining sections, and validating the final document through reader testing.

What is the best way to ensure technical proposals are reader-friendly?▼

The best way to ensure technical proposals are reader-friendly is to apply a reader testing stage, which validates the document's coherence and structure through iterative refinement based on target audience feedback.

Can I use this co-authoring workflow for decision docs and proposals?▼

Yes, you can use this co-authoring workflow for decision docs, proposals, RFCs, and technical specs. It triggers when you mention writing structured content and guides you through context gathering and refinement.

Do I need templates to start the documentation co-authoring process?▼

You need user input, templates, or context sources to start the documentation co-authoring process. The workflow requires these inputs to effectively scaffold the initial context gathering and subsequent drafting stages.