doc-coauthoring

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

Updated Dec 27, 2025
One-click install
npx skills add https://github.com/vardhan-harsha/helix --skill doc-coauthoring-vardhan-harsha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/vardhan-harsha/helix/tree/main/.agent/skills/doc-coauthoring
Command: npx skills add https://github.com/vardhan-harsha/helix --skill doc-coauthoring-vardhan-harsha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.

Core Features & Use Cases

  • Stepwise stages: Context Gathering, Refinement & Structure, Reader Testing.
  • Iterative drafting workflow with clarifying questions, brainstorming, curation, gap checks, drafting, and refinement.
  • Artifact-driven collaboration: creates structured outputs (artifacts) and iterates with user feedback.
  • Use cases include drafting technical specs, proposals, design docs, and RFCs in cross-functional teams.

Quick Start

Begin Stage 1: Context Gathering to collect context and align on goals for the document.

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 collaboratively?

Collaborative technical spec authoring requires a structured workflow guiding teams through context gathering, iterative drafting, and reader testing. This approach ensures cross-functional alignment and produces refined documentation artifacts through stage-wise refinement.

What is the best way to structure an iterative drafting workflow for proposals?

The best way to structure iterative drafting for proposals is using a multi-stage workflow separating context gathering, refinement, and structure. This method applies artifact scaffolding and gap checks to iteratively curate and refine document content.

Can I use a structured workflow to create RFCs for cross-functional teams?

Yes, you can use a structured workflow to create RFCs for cross-functional teams. The workflow guides collaborators through clarifying questions, brainstorming, and curation, specifically supporting the creation of technical specs, proposals, and RFCs.

How does reader testing work during document creation?

Reader testing works as a dedicated stage after context gathering and drafting refinement. It evaluates structured artifacts by testing them with readers, allowing authors to apply iterative edits based on feedback before finalizing documentation.

What are the limitations of using a stage-wise co-authoring workflow?

Stage-wise co-authoring workflows are suited for structured documents like technical specs and design docs, but may not fit quick informal notes. The staged process requires completing context gathering, refinement, and reader testing sequentially to yield proper artifacts.