taxonomy

Goal

Build a clear, comprehensive taxonomy for a given set of items, concepts, or domain

Scope

Use when you need to group, rank, or build a category structure from an existing list of items, concepts, or data

Execute

1. Define Taxonomy Purpose

Goal: Define the taxonomy's purpose and scope

1. Identify the domain or item set to categorize
2. Identify the audience and the taxonomy's objective
3. Decide the depth level (flattened, 1-level, multi-level)
4. Choose the primary criteria for categorization

2. Collect And Inspect Items

Goal: Gather and inspect the items to be taxonomized

1. List all existing items
2. Identify the key attributes of each item
3. Look for items that may be redundant or missing
4. Record the data sources

3. Group Items

Goal: Group items by the chosen criteria

1. Analyze attributes and relationships
2. Create categories per the selected criteria
3. Name each category clearly and without overlap
4. Place items into their fitting categories (allow cross-category placement when needed)

4. Build Hierarchy

Goal: Build the hierarchical structure

1. Identify top-level categories
2. Split into sub-categories where necessary
3. Place items in leaf nodes
4. Define relationships between categories (parent-child, sibling, dependency)

5. Label And Document

Goal: Make the taxonomy easy to use

1. Write a label and description for each category
2. Choose the output format: tree, table, tags, or markdown list
3. Provide examples for the key categories
4. Record conventions for adding new items

6. Validate And Refine

Goal: Check completeness

1. Verify every item is placed in a category
2. Verify categories don't overlap too much
3. Check consistency with the stated purpose
4. Refine the taxonomy from feedback or gaps found

Rules

1. Clarity And Non-Overlap

• The taxonomy must be clear, non-redundant, and comprehensive
• Use measurable criteria for categorization
• Avoid categories that are too broad or too narrow

2. Flexibility

• Support multi-parent or cross-cutting categories when needed
• Document labels, descriptions, and examples fully
• Version or timestamp the taxonomy if it changes often

3. Output Quality

• Output must be readable and actionable

• Match the output format to the audience

• Report gaps or items not yet fully categorized

• Use /grouping if needed

• Use /report if needed

Expected Outcome

• A complete, usable taxonomy
• Every item placed in a fitting category
• Categories with clear labels and descriptions
• Output in the chosen format (tree, table, tags, markdown)
• Guidance for adding/editing items in the future