documentation-writing

Coordinate collaborative documentation drafting through a three-phase review workflow.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/cjohnhanson/codelikecody --skill documentation-writing-cjohnhanson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-writing
Source: https://github.com/cjohnhanson/codelikecody/tree/main/.agents/skills/documentation-writing
Command: npx skills add https://github.com/cjohnhanson/codelikecody --skill documentation-writing-cjohnhanson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides teams to write project documentation collaboratively rather than delivering finished documents, reducing review back-and-forth and ensuring co-authorship.

Core Features & Use Cases

  • Enforces a section-by-section drafting process where the user directs and curates rather than receives a finished document.
  • Applies Diátaxis-based discipline, and project file conventions to ensure claims are source-verified.
  • Triggers when asked to write, draft, or create docs, guides, tutorials, references, or explanations.

Quick Start

Initiate a collaborative documentation draft by outlining sections and applying the three-phase workflow (Context, Structure and drafting, Review).

Frequently Asked Questions about documentation-writing

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

FAQPage Schema
How do I write project documentation collaboratively instead of just receiving a finished draft?

To write project documentation collaboratively, use a three-phase workflow of Context, Structure and drafting, and Review. This process enforces section-by-section co-authorship where you direct and curate content rather than receiving a completed document.

What is the Diátaxis framework and how does it apply to drafting tutorials and guides?

The Diátaxis framework is a documentation discipline that categorizes content into tutorials, guides, references, and explanations. Applying it during the drafting workflow ensures claims are source-verified and maintains consistent, traceable documentation across teams and projects.

How do I structure a collaborative writing workflow to ensure consistency and traceability?

Structure your collaborative writing workflow by enforcing a three-phase process: Context, Structure and drafting, and Review. Using frontmatter-driven discovery alongside this workflow ensures your documentation maintains consistency, traceability, and verifiability throughout the drafting lifecycle.

Can I use this collaborative drafting process for both technical references and team explanations?

Yes, you can use this collaborative drafting process for technical references and team explanations. The workflow triggers when asked to draft, review, or curate any documentation type, applying Diátaxis-based discipline to verify source claims across teams and projects.

Does collaborative documentation drafting reduce review back-and-forth across teams?

Collaborative documentation drafting reduces review back-and-forth by guiding teams through co-authorship. By enforcing a structured, section-by-section drafting process where users direct the content, it ensures claims are source-verified before final review.

What's the best way to start a collaborative documentation draft with my team?

The best way to start a collaborative documentation draft is by outlining sections and applying the three-phase workflow. You begin with Context, move to Structure and drafting, and finish with Review to ensure frontmatter-driven discovery and source verification.