Taxonomy

Taxonomy groups work by the goals, customers, products, skills, coding tools, and agents it relates to.

Taxonomy sits close to Initiatives because taxonomy terms make roadmap work easier to compare. A clear initiative explains the work. Taxonomy explains what the work affects and how it should roll up in Taxonomy Analytics.

Taxonomy types

Workspace owners define the taxonomy terms that fit the team. Terms can be nested, such as Platform > API, Hooli > Hooli Cloud, or Stability > Incident reduction. That gives Insights a rolled-up view and a more detailed breakdown.

Goals

Goals describe strategic outcomes. A goal should name the result the team wants, not the task category.

Example: use Stability to understand how much work contributes to reliability across initiatives, bugs, pull requests, and completed tasks.

Companies

Companies are customers, accounts, clients, or organizations affected by the work.

Example: use a company term to see how much work is spent for a specific customer, or nest divisions under a parent company when an account has multiple teams.

Products

Products are product lines, product areas, apps, platforms, or major surfaces.

Example: use Dashboard, API, or Mobile app to compare where roadmap work and completed work are concentrating.

Skills

Skills describe expertise, practice areas, or capability categories.

Example: use Security, Frontend, or Data to understand which skills are needed across planned work and where review load may concentrate.

Coding Tools

Coding Tools identify AI coding tools involved in delivery.

Example: use Coding Tools to see how work involving Cursor, Claude Code, Codex, or GitHub Copilot shows up across completed work and initiatives.

Agents

Agents identify agent profiles involved in the work.

Example: use Agents to review which local or cloud agent handled queued work and how that work appears in roadmap filters and Insights.

Automatic taxonomy signals

Some taxonomy can be inferred from captured work, such as coding tools or agent involvement.

Agent involvement can come from recognized AI coding activity and agent sessions. When an agent claims work linked to a child work item, that involvement can appear on the item and its parent initiatives so it is visible in roadmap filters and Insights.

You do not need to maintain every taxonomy term manually. Add the terms only the team can define, such as customers, goals, products, and skills. Let automatic signals cover execution details when they can be inferred reliably.

For automatic attribution, see Captured Work. For the complete taxonomy reference, see Taxonomy Types.