business

/business — Business Context Browser

Interactive browser for your organization's knowledge system. Explore terms, products, metrics, objectives, and team structure.

Scope

This skill browses the organization's documented knowledge in .knowledge/organizations/{org}/business/ (via helpers/knowledge/business_context.py). It never queries the dataset: /business products shows the product catalog YAML, not the products table. For what exists in the data, use /explore; for analysis history, /history.

Trigger

Invoked as /business or /business {subcommand}

Prerequisites

• Organization context must exist at .knowledge/organizations/{org}/
• Read .knowledge/setup-state.yaml to find active organization
• If no org configured: "No organization context found. Run /setup Phase 3 to configure business context, or create one manually at .knowledge/organizations/{name}/."`

Subcommands

/business (no args) — Overview

Display a summary of available business context:

📊 Business Context: {org_name}

  Glossary:    {n} terms defined
  Products:    {n} products cataloged
  Metrics:     {n} metrics specified
  Objectives:  {n} OKRs/goals tracked
  Teams:       {n} teams mapped

Type /business {category} for details.

Implementation:

1. Read .knowledge/setup-state.yaml to find active organization name
2. REQUIRED: Use helpers/knowledge/business_context.py → load_business_context(org_path) to load data
   • DO NOT manually read YAML files
   • The helper handles file not found errors, parsing errors, and provides consistent structure
3. Count entries in each category (glossary, products, metrics, objectives, teams)
4. Display summary table
5. If business context is empty or sparse (fewer than 3 categories populated):
   • Check .knowledge/analyses/index.yaml for past analyses
   • If analyses exist, add a section called "Implicit Knowledge (from Past Analyses)"
   • Extract and show:
     • Most frequently analyzed metrics (count mentions across analysis titles/tags)
     • Recurring business questions or themes
     • Common data gotchas from the active dataset's quirks.md
   • This helps new team members understand what the team actually measures, even when formal docs aren't populated yet
   • Frame this as "What the team measures (inferred from past work)" vs "Formal documentation (not yet configured)"
6. Always provide next steps: suggest /setup to populate formal context, or show how to add entries manually