document-generate

Audit project documentation against Diataxis quadrants and generate missing drafts.

15|5|Updated May 17, 2026
One-click install
npx skills add https://github.com/cropsgg/skills --skill document-generate-cropsgg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-generate
Source: https://github.com/cropsgg/skills/tree/main/skills/planning/document-generate
Command: npx skills add https://github.com/cropsgg/skills --skill document-generate-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits existing docs against the four Diataxis quadrants, identifies empty quadrants, and generates missing documentation from scratch. Each generated doc serves its quadrant's specific user need, with explicit audience, prerequisites, and usage context.

Core Features & Use Cases

  • Audit existing docs against the four Diataxis quadrants and map coverage.
  • Identify empty quadrants and define audience and use cases for each.
  • Prioritize and generate draft tutorials, how-tos, references, and explanations for targeted subsystems.
  • Produce end-to-end drafts with clear prerequisites, steps, expected outcomes, and troubleshooting guidance.

Quick Start

Ask this skill to audit a subsystem's docs and generate initial Diataxis coverage drafts.

Frequently Asked Questions about document-generate

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

FAQPage Schema
How do I audit project documentation against the Diataxis framework?

Auditing project documentation against the Diataxis framework involves mapping existing docs to the four quadrants to identify coverage gaps. This process categorizes current content into tutorials, how-tos, references, and explanations to highlight missing areas.

What is the Diataxis framework for technical documentation?

The Diataxis framework is a documentation strategy that categorizes content into four quadrants: tutorials, how-tos, references, and explanations. Each quadrant serves distinct user needs for learning, achieving goals, finding information, and understanding.

How do I generate missing documentation for a subsystem?

Generating missing documentation for a subsystem requires identifying empty Diataxis quadrants and defining target audience and use cases. The process produces end-to-end drafts with prerequisites, steps, expected outcomes, and troubleshooting guidance.

Can I use Diataxis coverage mapping for incomplete subsystem documentation?

Yes, Diataxis coverage mapping applies directly to subsystems with incomplete or missing documentation. It guides the targeted generation of tutorials, how-tos, references, and explanations tailored to each quadrant's specific user requirements.

What is the best way to identify documentation coverage gaps in a project?

The best way to identify documentation coverage gaps is mapping existing docs to the Diataxis quadrants. This reveals empty quadrants and produces an actionable plan highlighting missing tutorials, how-tos, references, and explanations.

What does a generated Diataxis documentation draft include?

A generated Diataxis documentation draft includes explicit audience definitions, prerequisites, step-by-step instructions, expected outcomes, and troubleshooting guidance. It serves the specific user need of its target quadrant.