doc-coauthoring

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

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/bakwankawa/lazy-code-skill --skill doc-coauthoring-bakwankawa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/bakwankawa/lazy-code-skill/tree/main/.cursor/skills/anthropic/doc-coauthoring
Command: npx skills add https://github.com/bakwankawa/lazy-code-skill --skill doc-coauthoring-bakwankawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users through a disciplined, collaborative approach to creating documentation, proposals, specs, and decision papers, ensuring clarity, alignment, and reader readiness.

Core Features & Use Cases

  • Structured workflow: Context Gathering, Refinement & Structure, and Reader Testing to iteratively build high-quality docs.
  • Trigger-based guidance: activates when writing or planning major documents, with stage-by-stage prompts and questions.
  • Reader-ready validation: tests the doc from a fresh reader perspective to surface gaps and ambiguities.

Quick Start

Start the workflow by initiating Stage 1: Context Gathering to collect context, define audience, and align goals before drafting.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I manage collaborative documentation workflows with multiple stakeholders?

A structured co-authoring workflow manages multiple stakeholders by enforcing three stages: context gathering, refinement and structure, and reader testing. It provides explicit questions and iteration controls to ensure clarity, traceability, and reader readiness across all contributors.

What is the best way to ensure technical specs are ready for readers before publishing?

Reader testing validates technical specs by evaluating the document from a fresh reader perspective to surface gaps and ambiguities. This workflow applies a dedicated testing stage that iteratively refines content until clarity and reader readiness requirements are met.

How do I start a structured co-authoring workflow for a proposal?

Start a structured co-authoring workflow for proposals by initiating Stage 1: Context Gathering to collect background context, define the target audience, and align goals before drafting begins. This ensures all stakeholders share a unified foundation before iterative refinement.

Can I use this documentation workflow for decision records and technical specs?

This documentation workflow supports decision records, technical specs, proposals, and substantial documentation. It activates when writing or planning major documents requiring context gathering, iterative refinement, and reader testing to ensure clarity and alignment.

When should I use a structured co-authoring workflow instead of drafting documents directly?

Use a structured co-authoring workflow when documents require context gathering, iterative refinement, and reader testing, especially when multiple stakeholders are involved. It enforces process-based discipline with explicit questions to ensure traceability that direct drafting lacks.