documentation-router

What problem does it solve?

Documentation tasks across projects often require manual routing to the correct workflow (code, project, release, or API documentation), causing delays and inconsistency.

Core Features & Use Cases

• Central routing: automatically directs documentation requests to the appropriate sub-skill (Code Documentation, Project Documentation, Release Documentation, API Documentation).
• Consistent triggers and outputs: standardizes how documents are created and described across categories.
• Use Case: route a request to generate a full API reference from an OpenAPI spec, or to add a new README section for a project.

Quick Start

Route a documentation request to the appropriate category (code, project, release, or API documentation) for processing.