doc-coauthoring

Name: doc-coauthoring
Availability: InStock
Author: LAI-YEN-CHUN

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

1|Updated Apr 21, 2025

Search Tags:#workflow #templates #documentation #iteration #coauthoring #reader-testing

Ready to run

npx skills add https://github.com/LAI-YEN-CHUN/VSCode-Settings --skill doc-coauthoring-lai-yen-chun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/LAI-YEN-CHUN/VSCode-Settings/tree/main/.github/skills/doc-coauthoring
Command: npx skills add https://github.com/LAI-YEN-CHUN/VSCode-Settings --skill doc-coauthoring-lai-yen-chun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, three-stage workflow to guide teams through collaborative document creation, ensuring context is captured, content is well-structured, and readers are validated.

Core Features & Use Cases

Stage 1: Context Gathering – capture goals, audience, constraints, and relevant background from all stakeholders.
Stage 2: Refinement & Structure – iteratively draft sections, organize content into a coherent outline, and harmonize terminology.
Stage 3: Reader Testing – validate the document with a fresh perspective to surface ambiguities and improve clarity.
Artifact & Guidance Support – optional artifacts and templates to support drafting without locking in a single format.
Use Case: Ideal for producing technical specs, proposals, design docs, PRDs, or decision records with an auditable collaboration trail.

Quick Start

Begin Stage 1 to gather context, then proceed to Stage 2 and Stage 3 with iterative refinements.

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 collaboratively without losing context?▼

Co-authoring technical specs without losing context requires a structured workflow that captures goals, audience, and constraints upfront. This skill guides teams through context gathering, iterative refinement, and reader testing to ensure consistent documentation.

What is the best way to structure a collaborative drafting workflow for proposals?▼

Structuring a collaborative drafting workflow for proposals is best achieved through a three-stage process: context gathering, structure refinement, and reader testing. This approach harmonizes terminology and validates clarity with a fresh perspective.

Can I use this structured documentation workflow for decision records and PRDs?▼

Yes, this structured documentation workflow supports decision records and PRDs. It applies stage-specific prompts and collaboration guardrails to coordinate context gathering and artifact management across various technical document types.

How do we validate document clarity during the co-authoring process?▼

Validate document clarity during the co-authoring process by applying a reader testing stage. This stage surfaces ambiguities and improves readability by reviewing drafted content with a fresh perspective before finalization.

Does this documentation workflow lock teams into a single template format?▼

No, this documentation workflow does not lock teams into a single template format. It provides optional artifacts and templates to support drafting and structure refinement while maintaining flexibility across different document types.