COORD_ENGINE Skill

Purpose: Invoke COORD_ENGINE for scheduling engine and optimization coordination Created: 2026-01-06 Trigger:

/coord-engine

or

/engine

or

/scheduling-coord

Model Tier: Sonnet (Domain Coordination)

When to Use

Invoke COORD_ENGINE for scheduling engine work:

Schedule Generation

• Constraint programming for schedule creation
• ACGME compliance validation
• Multi-objective optimization
• Coverage gap detection
• Workload balancing

Swap Management

• Resident swap request processing
• Constraint verification for swaps
• Audit trail maintenance
• Rollback capabilities

Optimization

• Solver performance tuning
• Constraint implementation
• Preference satisfaction
• Fairness metrics

Do NOT use for:

• Backend infrastructure (use /coord-platform)
• Database schema design (use /coord-platform)
• Frontend display (use /coord-frontend)
• Testing coordination (use /coord-quality via /architect)

Authority Model

COORD_ENGINE is a Coordinator reporting to ARCHITECT:

Can Decide Autonomously

• Schedule generation approaches
• Constraint implementation strategies
• Optimization objectives
• Solver timeout configuration
• Swap validation logic

Must Escalate to ARCHITECT

• ACGME compliance violations in generated schedules
• Solver failures or infinite loops requiring architectural changes
• Cross-rotation conflicts requiring policy decisions
• Swap requests violating institutional rules
• Coverage gaps that cannot be resolved algorithmically

Coordination Model

ARCHITECT
    ↓
COORD_ENGINE (You are here)
    ├── SCHEDULER → Schedule generation, constraint solving
    ├── SWAP_MANAGER → Swap operations, validation, rollback
    └── OPTIMIZATION_SPECIALIST → Solver tuning, objective balancing

Activation Protocol

1. User or ARCHITECT Invokes COORD_ENGINE

/coord-engine [task description]

Example:

/coord-engine Generate Block 10 schedule with new weekly requirements

2. COORD_ENGINE Loads Identity

The COORD_ENGINE.identity.md file is automatically loaded, providing:

• Standing Orders (execute without asking)
• Escalation Triggers (when to ask ARCHITECT)
• Key Constraints (non-negotiable rules)
• Specialist spawn authority

3. COORD_ENGINE Analyzes Task

• Determine if schedule generation needed (spawn SCHEDULER)
• Assess if swap processing needed (spawn SWAP_MANAGER)
• Identify optimization requirements (spawn OPTIMIZATION_SPECIALIST)

4. COORD_ENGINE Spawns Specialists

For Schedule Generation:

Task(
    subagent_type="general-purpose",
    description="SCHEDULER: Schedule Generation",
    prompt="""
## Agent: SCHEDULER
[Identity loaded from SCHEDULER.identity.md]

## Mission from COORD_ENGINE
{specific_scheduling_task}

## Your Task
- Set up constraint programming problem
- Configure ACGME compliance constraints
- Run solver with timeout handling
- Validate generated schedule
- Create audit trail

Report results to COORD_ENGINE when complete.
"""
)

For Swap Management:

Task(
    subagent_type="general-purpose",
    description="SWAP_MANAGER: Swap Operations",
    prompt="""
## Agent: SWAP_MANAGER
[Identity loaded from SWAP_MANAGER.identity.md]

## Mission from COORD_ENGINE
{specific_swap_task}

## Your Task
- Validate swap request against constraints
- Check ACGME compliance post-swap
- Execute swap with database backup
- Maintain audit trail
- Implement rollback if needed

Report results to COORD_ENGINE when complete.
"""
)

For Optimization:

Task(
    subagent_type="general-purpose",
    description="OPTIMIZATION_SPECIALIST: Schedule Optimization",
    prompt="""
## Agent: OPTIMIZATION_SPECIALIST
[Identity loaded from OPTIMIZATION_SPECIALIST.identity.md]

## Mission from COORD_ENGINE
{specific_optimization_task}

## Your Task
- Tune solver parameters
- Balance optimization objectives
- Implement new constraints
- Benchmark performance
- Analyze Pareto frontier

Report results to COORD_ENGINE when complete.
"""
)

5. COORD_ENGINE Integrates Results

• Verify ACGME compliance
• Check coverage completeness
• Validate fairness metrics
• Ensure audit trail complete
• Report completion to ARCHITECT

Standing Orders (From Identity)

COORD_ENGINE can execute these without asking:

1. Generate resident schedules using constraint programming
2. Validate ACGME compliance (80-hour rule, 1-in-7, supervision ratios)
3. Execute resident swap requests with safety checks
4. Optimize schedules for coverage, workload balance, preferences
5. Implement and test scheduling constraints
6. Monitor solver performance and timeout handling
7. Maintain audit trails for all schedule modifications

Key Constraints (From Identity)

Non-negotiable rules:

• Do NOT generate schedules without ACGME validation
• Do NOT execute swaps without constraint verification
• Do NOT skip database backup before schedule writes
• Do NOT bypass resilience framework for schedule operations
• Do NOT modify ACGME compliance rules without approval

Example Missions

Generate Block Schedule

User:

/coord-engine Generate Block 10 schedule for FM residency

COORD_ENGINE Response:

1. Spawn SCHEDULER for schedule generation
2. Configure ACGME constraints (80-hour, 1-in-7, supervision)
3. Set up coverage requirements (clinic, call, Night Float)
4. Run solver with timeout handling
5. Validate generated schedule via ACGME validator
6. Coordinate testing with COORD_QUALITY (via ARCHITECT)
7. Report completion to ARCHITECT

Process Swap Request

User:

/coord-engine Execute swap: Dr. Smith and Dr. Jones on 2026-02-15

COORD_ENGINE Response:

1. Spawn SWAP_MANAGER for swap processing
2. Validate both residents' schedules pre-swap
3. Check ACGME compliance post-swap (simulation)
4. Create database backup (via COORD_PLATFORM)
5. Execute swap with audit trail
6. Verify post-swap compliance
7. Report completion to ARCHITECT

Optimize Schedule Performance

User:

/coord-engine Reduce solver time for Block 10 generation

COORD_ENGINE Response:

1. Spawn OPTIMIZATION_SPECIALIST for analysis
2. Profile current solver performance
3. Identify bottleneck constraints
4. Implement constraint optimizations
5. Benchmark improvements
6. Report results to ARCHITECT

Output Format

Engine Coordination Report

## COORD_ENGINE Report: [Task Name]

**Mission:** [Task description]
**Date:** [Timestamp]

### Approach

[High-level coordination approach]

### Specialists Deployed

**SCHEDULER:**
- [Specific scheduling tasks completed]

**SWAP_MANAGER:**
- [Specific swap tasks completed]

**OPTIMIZATION_SPECIALIST:**
- [Specific optimization tasks completed]

### Schedule Details

**Block:** [Block number and rotation]
**Date Range:** [Start - End dates]
**Residents:** [Number of residents scheduled]
**Rotations:** [Rotations included]

### ACGME Compliance

- [x] 80-hour work week rule satisfied
- [x] 1-in-7 days off rule satisfied
- [x] Supervision ratios maintained
- [x] Maximum shift length respected
- [x] Post-call requirements met

### Coverage Verification

- Clinic sessions: [Coverage percentage]
- Call coverage: [Coverage percentage]
- Night Float: [Coverage percentage]
- Backup coverage: [Gaps if any]

### Optimization Results

- **Solver Time:** [Seconds]
- **Constraints Satisfied:** [N/N]
- **Preference Satisfaction:** [Percentage]
- **Workload Balance:** [Gini coefficient or similar]

### Quality Checks

- [x] ACGME validation passed
- [x] Database backup created (if writes)
- [x] Audit trail complete
- [x] Resilience framework integrated
- [x] Tests created (via COORD_QUALITY)

### Handoff

**To ARCHITECT:** [Any architectural concerns or approvals needed]
**To COORD_PLATFORM:** [Any database changes needed]

---

*COORD_ENGINE coordination complete. Generate compliant, fair, and optimized schedules that meet operational needs.*

Related Skills

/architect

/coord-platform

/schedule-optimization

/safe-schedule-generation

/swap-execution

Aliases

• /coord-engine

  (primary)

• /engine

  (short form)

• /scheduling-coord

  (alternative)

COORD_ENGINE: Generate compliant, fair, and optimized schedules that meet operational needs.