diataxis:plan

Classify documentation requests into Diátaxis quadrants and generate a writing plan.

2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/jayteealao/agent-skills --skill diataxis-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diataxis:plan
Source: https://github.com/jayteealao/agent-skills/tree/main/plugins/sdlc-workflow/skills/diataxis-doc-planner
Command: npx skills add https://github.com/jayteealao/agent-skills --skill diataxis-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify ambiguous or mixed documentation requests and propose a structured documentation approach using the Diátaxis model. It helps determine when to create tutorials, how-to guides, reference material, or explanations, and yields a practical writing plan and map.

Core Features & Use Cases

  • Classifies content into Diátaxis quadrants (Tutorial, How-to, Reference, Explanation) based on reader needs.
  • Proposes a documentation map and a practical writing plan with a clear ordering for deliverables.
  • Guides documentation projects from README rewrites to full documentation architectures, inventories, and audience-specific outcomes.

Quick Start

Provide your project name and target audience, and Diátaxis will generate a documentation plan.

Frequently Asked Questions about diataxis:plan

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

FAQPage Schema
How do I structure documentation using the Diátaxis framework?

To plan documentation using the Diátaxis model, classify mixed content requests into Tutorial, How-to, Reference, and Explanation quadrants. This approach separates learning-oriented material from practical guides and technical references to address distinct reader needs.

What is the best way to organize a documentation project for multiple audiences?

Organizing documentation for multiple audiences requires proposing a structured docs map and a practical writing plan. By mapping content to specific audience needs and applying Diátaxis quadrants, you can generate an execution order that prioritizes deliverables effectively.

How do I create a writing plan for a full documentation architecture?

Create a writing plan for a full documentation architecture by first conducting source inventories and classifying requests into Diátaxis quadrants. This yields a practical writing plan with a clear execution order for delivering structured documentation.

When do I need to write tutorials versus how-to guides in technical documentation?

You need to write tutorials when the goal is learning-oriented guidance, and how-to guides when the reader needs practical steps to achieve a specific task. Classifying content into these distinct Diátaxis quadrants clarifies documentation purpose and structure.

Can I use Diátaxis to plan a README rewrite?

Yes, you can use Diátaxis to plan a README rewrite. It guides documentation projects of varying scopes, from simple README rewrites to full documentation architectures, by classifying ambiguous content and proposing a structured docs map.

How do I classify ambiguous documentation requests into clear categories?

Classify ambiguous documentation requests by evaluating reader needs and sorting the content into Tutorial, How-to, Reference, and Explanation quadrants. This Diátaxis-driven classification determines the appropriate documentation type and proposes a structured approach.