doc-coauthoring

Guide collaborative document creation through context gathering, drafting, refinement, and validation workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams overcome the difficulty of creating clear, structured documents by guiding collaborative writing, context sharing, refinement, and reader validation.

Core Features & Use Cases

  • Context Gathering Workflow: Collect project background, audience needs, constraints, and supporting information before drafting.
  • Iterative Document Refinement: Develop proposals, technical specs, decision documents, and other structured content section by section with feedback loops.
  • Reader Testing: Validate documents by checking whether fresh readers can understand the content and identify gaps or ambiguities.

Quick Start

Use the doc-coauthoring skill to help me collaboratively create a technical specification document from my project notes.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I collaboratively write a technical specification document from rough project notes?

Collaborative technical specification writing is guided through structured context gathering, section-by-section drafting, iterative refinement, and reader validation to transform project notes into clear documents.

What is the best way to structure context gathering before drafting proposals and RFCs?

Context gathering for proposals and RFCs involves systematically collecting project background, audience needs, and constraints before drafting, ensuring all supporting information is structured for clear collaborative writing.

Can I use this coauthoring workflow to refine decision documents section by section?

Section-based editing for decision documents allows iterative refinement through feedback loops, enabling collaborators to develop and review structured content section by section until the document is clear.

Does reader testing help validate technical specs and identify content gaps?

Reader testing validates technical specs by checking whether fresh readers can understand the content, actively identifying gaps, ambiguities, or missing information before final approval.

When do I need a structured document workflow for proposals and technical specs?

A structured document workflow is needed for proposals and technical specs when multiple collaborators require systematic questioning, iterative editing, and reader testing to produce clear, approved content.

What are the limitations of guiding collaborative document creation without dedicated coauthoring tools?

Without structured coauthoring workflows, collaborative document creation lacks systematic questioning, section-based refinement, and reader testing, risking ambiguous proposals and unvalidated technical specs.