documentation-writer

Generate Diátaxis-compliant software documentation in Markdown.

182|8|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/compozy/agh --skill documentation-writer-compozy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-writer
Source: https://github.com/compozy/agh/tree/main/.agents/skills/documentation-writer
Command: npx skills add https://github.com/compozy/agh --skill documentation-writer-compozy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you produce clear, accurate, and user-focused software documentation by matching content to the right Diátaxis document type so readers can learn, solve problems, look things up, or understand concepts efficiently.

Core Features & Use Cases

  • Diátaxis-aligned writing: Produces documentation that is explicitly organized into Tutorials, How-to Guides, Reference, and Explanations with the correct intent for each.
  • Request-driven workflow: Clarifies the document type, audience, user goal, and scope before drafting, reducing mismatches between what you want and what the doc delivers.
  • Quality-focused consistency: Maintains coherent terminology, tone, and structure, improving maintainability and reader trust.

Use case example: You need onboarding materials for a new AGH feature, a step-by-step guide to perform a common setup task, a reference page describing CLI options, and an explanation of how the underlying concept works.

Quick Start

Ask the skill to create a Diátaxis Tutorial for the documentation of a new feature, including the target audience, the user’s goal, and what should be in or out of scope.

Frequently Asked Questions about documentation-writer

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

FAQPage Schema
What is the best way to structure technical documentation for different reader intents?

The Diátaxis framework structures technical documentation into four types—Tutorials, How-to Guides, Reference, and Explanations—each serving a distinct reader intent like learning, problem-solving, or lookup. This approach matches content to user goals efficiently.

How do I write a Diátaxis-compliant tutorial for a new software feature?

To write a Diátaxis-compliant tutorial, specify the target audience, the user's learning goal, and the scope. The skill clarifies these elements, proposes a structure for approval, then generates Markdown content with consistent terminology and tone.

When should I use a how-to guide instead of an explanation in software documentation?

Use a how-to guide when the reader needs step-by-step instructions to solve a specific problem, and use an explanation when they need to understand underlying concepts. The skill selects the appropriate Diátaxis document type based on the requested user goal.

Can I generate reference documentation for CLI options using the Diátaxis framework?

Yes, you can generate reference documentation for CLI options. The skill treats reference material as a distinct Diátaxis type, requiring you to define the audience and scope before producing accurate, lookup-focused Markdown content.

Does this documentation writing approach require a specific platform or framework?

No specific platform or framework is required. The skill operates independently to produce Markdown content, requiring only the document type, audience, goal, and scope to draft Diátaxis-compliant software documentation.