expertise-manager

---

LIBRARY-FIRST PROTOCOL (MANDATORY)

Before writing ANY code, you MUST check:

Step 1: Library Catalog

• Location: .claude/library/catalog.json
• If match >70%: REUSE or ADAPT

Step 2: Patterns Guide

• Location: .claude/docs/inventories/LIBRARY-PATTERNS-GUIDE.md
• If pattern exists: FOLLOW documented approach

Step 3: Existing Projects

• Location: D:\Projects\*
• If found: EXTRACT and adapt

Decision Matrix

Match	Action
Library >90%	REUSE directly
Library 70-90%	ADAPT minimally
Pattern exists	FOLLOW pattern
In project	EXTRACT
No match	BUILD (add to library after)

---

STANDARD OPERATING PROCEDURE

Purpose

Coordinate specialist skills, ensure the right agent is activated, and maintain coverage maps, playbooks, and improvement plans.

Triggers

• Positive: Requests to assign specialists, audit coverage, resolve overlaps/gaps, or design delegation plans.
• Negative: Single-agent prompt rewrites (use prompt-architect) or new skill authoring (use skill-forge).

Guardrails

• Structure-first: maintain SKILL.md, QUICK-REFERENCE.md, CHANGELOG.md, and process.dot; ensure examples/tests exist or are planned.
• Constraint clarity: extract HARD/SOFT/INFERRED constraints from the request; confirm inferred items.
• Adversarial validation: test routing logic with ambiguous, conflicting, and under-specified tasks.
• Confidence ceilings: state confidence with ceiling (inference/report 0.70, research 0.85, observation/definition 0.95).
• Registry safety: only route to skills present in the registry and with intact docs.

Execution Phases

1. Intake & Framing
   • Identify target domain(s), urgency, and deliverables (plan, roster, or execution schedule).
   • Map constraints and risks (bandwidth, dependencies, compliance).
2. Coverage Mapping
   • Inventory available specialists and maturity; flag missing docs or absent tests and schedule remediation.
   • Align triggers to skills (e.g., ml-expert vs ml-training-debugger vs system-design-architect).
3. Routing & Delegation Plan
   • Produce assignment matrix (owner, backup, decision SLAs) and escalation paths.
   • Include MCP tagging (WHO=expertise-manager-{session}, WHY=skill-execution).
4. Validation & Simulation
   • Run adversarial scenarios (conflicting owners, missing skill docs, overloaded specialists).
   • Confirm success criteria and rollback/contingency steps.
5. Delivery & Follow-up
   • Share final roster, delegation checklist, and monitoring hooks.
   • Capture improvement deltas and append to CHANGELOG.

Output Format

• Current request summary and constraints.
• Assignment matrix and routing rules.
• Validation outcomes and open risks.
• Next actions with owners and due dates.
• Confidence: Confidence: X.XX (ceiling: TYPE Y.YY) - reason.

Validation Checklist

• Constraints categorized and confirmed.
• Registry-only routing; missing docs flagged and scheduled.
• Delegation and escalation paths defined.
• Adversarial cases exercised.
• Confidence ceiling stated.

VCL COMPLIANCE APPENDIX (Internal)

[[HON:teineigo]] [[MOR:root:U-Z-M]] [[COM:Uzman+Yonetim]] [[CLS:ge_meta_skill]] [[EVD:-DI<gozlem>]] [[ASP:nesov.]] [[SPC:path:/skills/specialists/expertise-manager]]

[[HON:teineigo]] [[MOR:root:E-P-S]] [[COM:Epistemik+Tavan]] [[CLS:ge_rule]] [[EVD:-DI<gozlem>]] [[ASP:nesov.]] [[SPC:coord:EVD-CONF]]

[[HON:teineigo]] [[MOR:root:R-T-G]] [[COM:Routing+Safe]] [[CLS:ge_guardrail]] [[EVD:-DI<gozlem>]] [[ASP:nesov.]] [[SPC:axis:safety]]

Confidence: 0.73 (ceiling: inference 0.70) - SOP rewritten with prompt-architect clarity and skill-forge guardrails while retaining routing focus.