doc-coauthoring

Guide structured documentation co-authoring through three workflow stages.

Updated Jun 8, 2025
One-click install
npx skills add https://github.com/noartem/kawa --skill doc-coauthoring-noartem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/noartem/kawa/tree/main/ui/.ai/skills/doc-coauthoring
Command: npx skills add https://github.com/noartem/kawa --skill doc-coauthoring-noartem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users through a structured workflow to co-author documentation, helping teams produce clearer, more reader-friendly content with fewer revision cycles.

Core Features & Use Cases

  • Structured three-stage workflow: Context Gathering, Refinement & Structure, Reader Testing, to guide problem framing, content iteration, and reader validation.
  • Trigger-driven offers: suggests starting the workflow when users mention writing docs, proposals, technical specs, or decision docs.
  • Collaboration-ready artifacts: supports staged drafting, feedback, and verification to improve readability and maintainability.

Quick Start

Offer this three-stage workflow whenever a user begins a documentation task, then start at Stage 1: Context Gathering.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
What is the best way to co-author technical specs and proposals with a team?

Co-authoring technical specs and proposals works best using a structured three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This enforces problem framing, content iteration, and reader validation to produce clear documentation.

How do I start writing documentation with a three-stage workflow?

To start writing documentation with a three-stage workflow, begin at Stage 1: Context Gathering to frame the problem. The workflow is triggered automatically whenever you mention writing docs, proposals, technical specs, or decision docs.

Can I use this workflow for decision docs and structured proposals?

Yes, you can use this workflow for decision docs and structured proposals. It is designed for collaborative writing tasks and supports staged drafting, feedback, and verification to improve readability and maintainability across various structured content.

Why does reader testing matter for documentation collaboration?

Reader testing matters for documentation collaboration because it validates content readability and reader-friendliness. As the third stage of the coauthoring workflow, it helps teams catch issues early, reducing revision cycles and improving final maintainability.

Does this documentation workflow require any external dependencies?

No, this documentation workflow does not require any external dependencies or components. It operates independently to guide teams through context gathering, refinement, and reader testing without needing additional tool integrations.