extension-combo-engine

Coordinating multiple Claude Code extensions requires mapping a compound request to a unified system with explicit wiring. The engine produces a blueprint defining components, data flow, and install order for phased generation across 2-4 cross-referencing extensions.

Extension orchestration establishes explicit data flow between hooks, skills, and references across multiple extensions. You need it when a compound intent requires 2-4 extensions that reference each other to function as a coordinated system.

Yes, you can generate a coordinated blueprint defining wiring and install order for cross-extension hooks and skills. It handles compound intents routed for Tier 2 scenarios, producing a phased generation plan for 2-4 integrated components.

Wiring data flow between components is handled by generating a blueprint that establishes explicit connections across hooks, skills, and references. The engine maps compound intents to define component relationships and phased install order.

This coordination mechanism is limited to Tier 2 scenarios supporting 2-4 extensions that reference each other. It handles compound intents routed by smart-scaffold or extension concierge, not single extension or larger unstructured generation tasks.