doc-coauthoring

Guides users through a three-stage workflow for drafting technical documents and proposals.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/salmanparacha/speckitplus-calculator --skill doc-coauthoring-salmanparacha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/salmanparacha/speckitplus-calculator/tree/main/.claude/skills-nocontext/doc-coauthoring
Command: npx skills add https://github.com/salmanparacha/speckitplus-calculator --skill doc-coauthoring-salmanparacha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Co-authoring documentation often suffers from context gaps, misalignment among contributors, and readability issues for readers. This skill provides a structured three-stage workflow that guides teams through Context Gathering, Refinement & Structure, and Reader Testing to produce coherent, reader-ready documents.

Core Features & Use Cases

  • Stage-based guidance covering Context Gathering, Refinement & Structure, and Reader Testing.
  • Interactive clarifying questions, iterative drafting, and surgical edits to shape each section.
  • Artifacts scaffolds and templates to organize proposals, technical specs, decisions, and related docs.

Quick Start

Begin Stage 1 by outlining the document goal, audience, and initial clarifying questions.

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 documentation without misalignment among contributors?

Structured co-authoring of technical documentation prevents contributor misalignment by guiding teams through interactive context gathering, iterative refinement, and reader testing stages to produce coherent documents.

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

A structured collaborative drafting workflow for proposals and RFCs uses a three-stage process: initial context gathering, iterative refinement with surgical edits, and final reader testing to ensure readability.

How do I gather context and clarify goals before drafting technical specs?

Gather context for technical specs by outlining the document goal and audience first, then generating interactive clarifying questions to resolve gaps before moving to iterative refinement and structure.

Can I use this guided workflow for decision records and technical docs?

Yes, this guided workflow applies to drafting decision records, technical docs, proposals, and RFCs, providing artifact scaffolds and templates to organize related documents and ensure reader-ready outputs.

How do I test if my documentation is readable for the target audience?

Test documentation readability by applying the reader testing stage of the co-authoring workflow, which evaluates the refined draft against the target audience to ensure the final document is reader-ready.

Why does my co-authored documentation have context gaps and readability issues?

Co-authored documentation often suffers from context gaps and readability issues due to a lack of structured refinement, which can be resolved using stage-based guidance and iterative drafting techniques.