governing-taxonomy

Design documentation taxonomy models with split/nest rules and metadata schemas.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/musher-dev/bundles --skill governing-taxonomy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: governing-taxonomy
Source: https://github.com/musher-dev/bundles/tree/main/developer-docs-authoring/skills/governing-taxonomy
Command: npx skills add https://github.com/musher-dev/bundles --skill governing-taxonomy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to designing and governing documentation taxonomy, ensuring content is organized logically, discoverable, and scalable. It addresses the challenges of content categorization, splitting/nesting, metadata schemas, and controlled vocabularies.

Core Features & Use Cases

  • Taxonomy Model Design: Frameworks for task-based, topic-based, and hybrid models.
  • Content Organization Rules: Decision trees and thresholds for splitting or nesting content.
  • Metadata Schema: Defines essential and recommended metadata for pages.
  • Controlled Vocabulary: Guidelines for establishing and enforcing label consistency.
  • Governance Board: Process for managing taxonomy decisions and changes.
  • Use Case: When planning a new documentation site or restructuring an existing one, use this skill to define the core categories, decide how to group related topics, and establish rules for future content additions.

Quick Start

Use the governing-taxonomy skill to define a hybrid taxonomy model for organizing documentation.

Frequently Asked Questions about governing-taxonomy

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

FAQPage Schema
How do I decide between task-based and topic-based categorization for documentation?

Documentation taxonomy design chooses task-based categorization for workflow-driven content, topic-based for reference material, or hybrid models combining both. The decision depends on whether users navigate by specific goals or browse by subject area to ensure logical content discoverability.

What are the rules for splitting or nesting content categories in information architecture?

Content organization rules provide decision trees and thresholds for splitting or nesting documentation categories. These criteria prevent shallow categories and excessive nesting depth, ensuring the information architecture scales logically without overwhelming users navigating the hierarchy.

How do I create a metadata schema and controlled vocabulary for content strategy?

Define a metadata schema by specifying essential and recommended page metadata, then establish a controlled vocabulary to enforce label consistency. This combination standardizes content strategy practices, making documentation predictable and easier to discover across the site.

What is a taxonomy governance board and when do I need one for documentation?

A taxonomy governance board manages documentation categorization decisions and structural changes over time. You need one when planning a new documentation site or restructuring an existing one to maintain metadata schemas, enforce labeling conventions, and process future content additions.

Does this documentation taxonomy approach support hybrid categorization models?

Yes, the taxonomy design framework explicitly supports hybrid models that merge task-based and topic-based categorization. This approach accommodates complex content strategy requirements by allowing flexible grouping of related topics within a unified documentation structure.