doc-coauthoring

Gather audience, purpose, source material, and format to create documentation.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bennybennison/agent-toolkit --skill doc-coauthoring-bennybennison
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/bennybennison/agent-toolkit/tree/main/skills/doc-coauthoring
Command: npx skills add https://github.com/bennybennison/agent-toolkit --skill doc-coauthoring-bennybennison

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many documentation efforts produce technically correct but practically unusable docs because they skip crucial context gathering and lack testing from a reader's perspective.

Core Features & Use Cases

  • Three‑stage workflow: Context gathering, drafting & refinement, and reader testing.
  • Guidance for each stage: Audience identification, purpose definition, source material collection, format selection, outline creation, progressive disclosure, consistency checks, and self / cross‑agent testing.
  • Applicable scenarios: Writing new READMEs, AGENTS.md, SKILL.md, tutorials, ADRs; rewriting confusing docs; collaborating with humans where the agent drafts and the human refines; onboarding projects lacking documentation.

Quick Start

Ask the doc‑coauthoring skill to help you create a clear README for your new project.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I create clear and actionable documentation from rough drafts?

Clear documentation requires gathering audience, purpose, source material, and format, then applying a three-stage workflow of context gathering, drafting, and reader testing.

What is the best way to write a README for a new project?

Writing a README involves identifying audience and purpose, collecting source material, selecting a format, and testing the draft from a reader's perspective.

How does a three-stage documentation workflow improve technical authoring?

A three-stage workflow improves authoring by separating context gathering, drafting with progressive disclosure, and consistency checks from reader testing, preventing unusable docs.

Do I need any external dependencies or specific tools for documentation collaboration?

No external dependencies are needed for documentation collaboration; the workflow operates using plain markdown prompts to guide drafting and refinement between agents and humans.

Can I use this workflow to rewrite confusing tutorials and onboarding docs?

Yes, you can use the workflow to rewrite confusing tutorials and onboarding docs by redefining the audience, clarifying purpose, and running cross-agent testing.

Why does my technically correct documentation remain unusable for readers?

Technically correct documentation remains unusable when it skips crucial context gathering and lacks testing from a reader's perspective to ensure actionable clarity.