Dispatcher

MANDATORY first step before selecting any skill. Contains the complete routing table for all 61+ skills. The system prompt only shows ~50 skills — this file is the single source of truth.

IMPORTANT: Always Load First

Claude Code has a ~50 skill limit in the system prompt. Skills beyond this limit are silently dropped. The dispatcher contains the COMPLETE routing table. Always consult this file before choosing a skill, especially for:

• Sending emails → email-send-direct (NOT email-send-bulk)
• Call preparation → call-prep
• Document/rekvizity requests → documents

When to use

• ALWAYS — before selecting a skill for any task
• Task requires 2+ skills (e.g.: query CRM -> send telegram)
• It's unclear which skill is needed
• An execution plan is needed for a complex task

Step 1: Analyze the task

Determine:

• Domain: CRM, PM, Sales, Channels, Finance, Dev, Infra, Legal, Agents?
• Action: read, create, update, send, review, deploy, monitor?
• Object: company, person, task, message, invoice, document, agent?

Step 2: Skill Routing Table

CRM — Contacts & Relationships

PM — Tasks & Projects

Sales — Consulting & Client Work

Channels — Communication

Finance — Invoices & Payments

Dev — Code & Deployment

Infra — Tools & Auth

Legal

Agents — Autonomous Runners

Documents & Data

Core — Always Available

Step 3: Multi-Skill Orchestration

Examples of combinations:

"Send all clients a message about new prices"

1. query-leads → get clients (relationships/clients.csv)
2. For each → find contact (contacts/people.csv)
3. telegram-send / email-send-bulk → send
4. log-activity → record in activities.csv

"Good morning, what's new?"

1. daily-briefing → tasks + email + follow-ups

"Prepare for a call with X and send the agenda"

1. call-prep → research + plan (includes workspace check)
2. email-send-direct → send agenda
3. log-activity → record activity

"Client sent a list of automation requests"

1. query-leads → get CRM context
2. client-discovery → analyze requests, estimate hours, prioritize
3. client-workspace → create shared questionnaire doc
4. log-activity → record activity

"Set up folder for new client"

1. query-leads → get company + contact email
2. client-workspace → create folder structure + share
3. log-activity → record activity

"Generate and send invoice to client"

1. query-leads → get client + billing info
2. invoice-generator-agent → generate invoice
3. google-drive → upload to client folder
4. email-send-direct → send to client
5. log-activity → record

"Deploy website changes"

1. code-review → check changes
2. git-workflow → branch + PR
3. deploy-website → deploy via Cloud Build

"Review this NDA and send feedback"

1. legal-review → analyze document
2. email-send-direct → send feedback
3. log-activity → record

"Send rekvizity / passport data to partner"

1. documents → read structured data blocks
2. email-send-direct → send (reply to thread)
3. log-activity → record

"User provides document scans"

1. documents → extract data, upload scans to Drive
2. Update passport_data.md with structured data

Step 4: Execute

• Simple task → execute immediately
• Complex task → load skill via Read tool
• Multi-step → create a plan, execute sequentially

Post-Execution Checklist

After executing a task that modifies data:

What changed?
      │
      ├── DATA (CSV in CRM/PM)?
      │         ↓
      │    change-review → git-workflow
      │
      └── CODE (*.py, *.js, *.md)?
                ↓
           code-review → git-workflow

If there was outreach (email/telegram/call):

1. Add a record in activities.csv (log-activity)
2. Update task in pm_tasks_master.csv
3. change-review → PR → merge

If CRM/PM data was modified:

1. Validation against schema.yaml
2. change-review → PR → merge

If code or skills were modified:

1. code-review → PR → merge

Data Paths

New Skill Registration Checklist

When creating a new skill, ALWAYS complete ALL steps:

1. Create SKILL.md in ~/claude-skills/skills/{category}/{skill-name}/SKILL.md

   • Use template: ~/claude-skills/skills/TEMPLATE.md
   • Must have frontmatter with name and description

2. Create symlink: ln -s ~/claude-skills/skills/{category}/{skill-name} ~/.claude/skills/{skill-name}

3. Update THIS dispatcher:

   • Add to the correct section in Step 2 Routing Table
   • Add orchestration example in Step 3 if relevant

4. Verify discovery:

   • Check if skill appears in system prompt (it won't if >50 skills)
   • If NOT visible — that's OK, dispatcher covers it

5. Commit via git-workflow: branch → PR → merge

CRITICAL: Steps 3-4 are what gets forgotten. If you skip updating the dispatcher, the skill becomes invisible when the system prompt drops it.

When dispatcher is NOT needed

• User explicitly says which skill ("load telegram-send")
• Simple answer to a question (no actions required)
• Continuation of a previous task (context already exists)