experts

Expert Registry

Extensible expert system for panel-based analysis skills (spec-panel, business-panel, and custom panels).

Directory Structure

experts/
├── README.md              # This file
├── registry.yaml          # Master index — auto-generated, do not edit manually
├── panels/                # Panel definitions — which experts sit on which panel
│   ├── spec-panel.yaml
│   └── business-panel.yaml
├── packs/                 # Thematic bundles — groups of related experts
│   ├── core-engineering.md
│   └── core-business.md
└── individuals/           # One file per expert — the source of truth
    ├── karl-wiegers.md
    └── _TEMPLATE.md       # Copy this to create a new expert

How It Works

1. Experts live in individuals/ — one markdown file per expert with structured frontmatter
2. Packs live in packs/ — thematic bundles that group related experts
3. Panels live in panels/ — YAML files that define which experts (or packs) sit on a panel, plus auto-select rules
4. Registry is the master index — regenerated by running scripts/rebuild-registry.sh

Adding a New Expert

cp individuals/_TEMPLATE.md individuals/your-expert.md
# Edit the file, then rebuild:
./scripts/rebuild-registry.sh

Adding a New Pack

cp packs/_TEMPLATE.md packs/your-domain.md
# Edit the file, then rebuild

Adding a New Panel

cp panels/_TEMPLATE.yaml panels/your-panel.yaml
# Edit the file, then rebuild

Auto-Select

Panels can define keyword rules that automatically add relevant experts based on the task description. See panels/_TEMPLATE.yaml for the format.

Token Budget

Each expert costs ~200-500 tokens in the assembled prompt. Panels enforce a max-experts cap (default: 6) to prevent token bloat. Auto-selected experts are added only if the panel hasn't hit the cap.