docs-management

Create understanding-oriented explanation documentation following the Diataxis framework. Explanations clarify concepts, architecture, and design decisions.

Create task-oriented how-to guide documentation following the Diataxis framework. How-to guides help users accomplish specific goals.

Create information-oriented reference documentation following the Diataxis framework. Reference docs provide factual, complete information for lookup.

Create learning-oriented tutorial documentation following the Diataxis framework. Tutorials help users learn by doing with step-by-step guidance.

Display help and usage information for the docs-management plugin. Optionally specify a command or skill name for detailed help.

Analyze existing project documentation and migrate it to the standard Diataxis-based structure. Creates a migration plan before making changes.

Audit current project documentation to identify gaps, outdated content, and areas needing improvement. Provides a coverage report with recommendations.

Initialize the standard documentation directory structure in a new project following the Diataxis framework and documentation standards.

Review recent git commits and update project documentation based on new features, bug fixes, or changes. Automatically determines which doc types need updating.

Expert documentation engineer specializing in technical documentation systems using the Diataxis framework. Coordinates documentation assessment, creation, and organization following industry standards.

Guidelines for creating Architecture Decision Records (ADRs). Use when documenting significant architectural decisions, their context, alternatives considered, and consequences.

Documentation standards and conventions based on Diataxis framework. Use this skill to learn project documentation conventions before creating, reviewing, or updating docs.

Guidelines for creating task-oriented how-to guide documentation. Use when writing content that helps users accomplish specific goals.

Guidelines for documenting research findings and investigation results. Use when writing content about discoveries, analysis, and recommendations from code analysis, API testing, or other research.

Guidelines for creating architecture overview and system explanation documentation. Use when writing content that clarifies system design, data flow, and architectural concepts.

Guidelines for creating technical specification and API reference documentation. Use when writing factual, complete content about data models, API contracts, and configuration options.

Guidelines for creating learning-oriented tutorial documentation. Use when writing step-by-step content that helps users learn by doing.