integration-strategy

name	integration-strategy
description	Blueprint for integrating new skills into Family Doctor. Use when adding a new skill, modifying routing rules, or planning how skills connect to the orchestrator. Triggers on "add new skill", "integrate", "routing", "how do skills connect".
allowed-tools	["bash","glob","read"]
version	1.0.0

Integration Strategy

Blueprint for integrating new skills into the Family Doctor suite.

When to Use

• Adding a new skill to the family-doctor ecosystem
• Modifying how skills connect to the orchestrator
• Planning routing rules for new capabilities
• Designing data contracts between skills

Skill Types in Family Doctor

Type	Examples	Routing
Orchestrator	family-doctor	Entry point, routes to others
Clinical	chronic-care, vital-monitor	Health domain skills
Lifestyle	nutrition-advisor, fitness-coach	Behavioral skills
Mental Health	mental-health	Psychological skills
General-Core	pubmed-search, general-browser-search	External knowledge
Support	care-coordinator, emergency-preparedness	Coordination skills

Integration Checklist

1. Create Skill File

Create family-doctor/[skill-name]/SKILL.md:

---
name: [skill-name]
description: One-line description. Triggers on keywords.
allowed-tools: [tool1, tool2]
---

# [Skill Name]

... detailed instructions ...

2. Add to Routing Table

Update family-doctor/SKILL.md routing table with:

• Entry trigger pattern (regex or keywords)
• Parent skill (usually "family-doctor")
• Output contract format

3. Define Data Contracts

Input Contract

{
  "query": "string",
  "context": "object",
  "preferences": "object"
}

Output Contract

{
  "query": "string",
  "results": [],
  "confidence": 0.0-1.0,
  "authorization": "session-wide|per-query|none"
}

4. Configure Authorization

All external skills must support:

Mode	Behavior
session-wide	User consented once for all queries this session
per-query	User approves each query individually
none	No external access (default)

5. Define Reference Schema

For health data:

{
  "id": "uuid",
  "topic": "string",
  "query": "string",
  "date": "YYYY-MM-DD",
  "sources": ["source names"],
  "summary": "string"
}

Store at: health/References/

Routing Priority

Lower number = checked first:

Skill	Priority	Reason
family-doctor	0	Entry point
general-browser-search	10	External guidelines
pubmed-search	20	Literature
clinical skills	30	Domain-specific
lifestyle skills	40	Behavioral
support skills	50	Coordination

Conflicts to Avoid

New Skill	Don't Overlap With
general-browser-search	pubmed-search (different sources)
pubmed-search	general-browser-search
clinical skills	Each other in same domain

Testing Integration

1. Verify skill file loads correctly
2. Test routing from family-doctor entry point
3. Test authorization flow
4. Verify citation output to health/References/
5. Check data contract compliance