docs-stage-routing

Define a repository-local routing contract for document-generation workflows.

1|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/buenhyden/hy-home.k8s --skill docs-stage-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-stage-routing
Source: https://github.com/buenhyden/hy-home.k8s/tree/main/.agents/skills/docs-stage-routing
Command: npx skills add https://github.com/buenhyden/hy-home.k8s --skill docs-stage-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines a repository-local routing contract for document-generation workflows, ensuring requests are consistently directed to the correct templates and stage structures.

Core Features & Use Cases

  • Enforces routing to canonical docs stage trees and templates.
  • Provides guidance for updating folder READMEs when new authored documents are created.
  • Reroutes non-canonical targets to appropriate governance paths and prevents parallel docs trees.

Quick Start

Route a sample document request through the canonical docs stage tree using the defined templates.

Frequently Asked Questions about docs-stage-routing

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

FAQPage Schema
How do I enforce document routing to canonical templates in a repository?

Document routing governance applies a repository-local contract to classify requests and map them to canonical stage trees and templates, preventing parallel docs trees.

What is the best way to update folder READMEs when adding new documentation?

Folder README updates are governed by a routing contract that provides guidance for updating them automatically when new authored documents are created in the stage tree.

How do I reroute non-canonical document targets to proper governance paths?

Rerouting non-canonical targets requires a routing contract that identifies non-canonical requests and redirects them to appropriate governance paths to prevent parallel docs trees.

How do I validate required headings and status in documentation workflows?

Heading and status validation uses a governance routing contract that enforces status rules and required headings, providing validation evidence for document generation workflows.

Does document governance work with existing repository templates?

Yes, document governance works with existing repository templates by applying template mapping to classify requests and route them to correct templates within the canonical stage tree.

Why do I need a routing contract for documentation workflows?

A routing contract ensures requests are consistently directed to correct templates and stage structures, preventing parallel docs trees and maintaining governance across document generation.