doc-coauthoring

Coordinate context gathering, refinement, and reader testing for multi-stakeholder documents.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/fajshah/hackhathone-2-phase-5 --skill doc-coauthoring-fajshah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/fajshah/hackhathone-2-phase-5/tree/main/skills/doc-coauthoring
Command: npx skills add https://github.com/fajshah/hackhathone-2-phase-5 --skill doc-coauthoring-fajshah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eliminates the inefficiency of multi-stakeholder document creation. This skill provides a structured three-stage workflow to gather context, iteratively refine content, and test readability, ensuring high-quality documents that readers can understand and contribute to.

Core Features & Use Cases

  • Guided Context Gathering: collects relevant background, audience, and constraints from all stakeholders.
  • Refinement & Structure: collaboratively builds sections, handles feedback, and maintains version coherence.
  • Reader Testing: validates clarity and completeness with a fresh reader perspective before publication.

Quick Start

Accept the three-stage workflow and begin Stage 1: Context Gathering by providing initial context about the document.

Frequently Asked Questions about doc-coauthoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a structured co-authoring workflow for multi-stakeholder documents?

A structured co-authoring workflow coordinates Context Gathering, Refinement & Structure, and Reader Testing across collaborators to produce technical specs, proposals, design docs, and decision records efficiently.

How do I start co-authoring a technical spec with multiple stakeholders?

Begin co-authoring a technical spec by initiating Stage 1: Context Gathering to collect relevant background, audience details, and constraints from all stakeholders before iteratively refining the document structure.

Can I use this workflow to create design docs and decision records?

Yes, you can use this workflow to create design docs and decision records, as it applies stage-specific questions, iterative drafting, and artifact-based collaboration to coordinate multi-stakeholder document creation.

What is the best way to validate document clarity before publication?

The best way to validate document clarity is Reader Testing, which checks readability and completeness from a fresh reader perspective to ensure high-quality documents that readers can understand and contribute to.

How does iterative drafting handle feedback during document refinement?

Iterative drafting handles feedback during Refinement & Structure by collaboratively building sections and maintaining version coherence while applying clear guardrails and quality checks to the multi-stakeholder document.

When do I need a structured workflow for multi-stakeholder document creation?

You need a structured workflow for multi-stakeholder document creation when inefficiencies arise in gathering context, refining content across collaborators, and testing readability for technical specs, proposals, design docs, and decision records.