capability-discovery

Dynamically discover installed plugins by triggering a runtime scan that enumerates available extensions and builds a capability registry for adaptive task routing. This maps plugins to abstract categories, allowing workflows to assign tasks without hardcoding plugin names.

Capability mapping works by scanning installed plugins at runtime and categorizing them into a registry of abstract capabilities. The routing mechanism then matches incoming tasks to the most suitable agent based on project type and declared capabilities.

Yes, you can route tasks to specific agents based on project type. The routing mechanism evaluates the current project context and prefers compatible plugins from the capability registry to ensure the most suitable agent handles the task.

The best way to handle task delegation when no plugin matches is to use the built-in graceful fallback mechanism. When the capability registry finds no suitable plugin for a task, the system transparently falls back to default built-in agents.

Yes, plugin discovery supports runtime refresh and re-discovery. You can trigger the discovery flow at any time to enumerate newly installed plugins, refresh the capability map, and update the routing rules dynamically without restarting.

Explicit delegation announcements are used during task routing to provide transparency and improve user awareness of routing decisions. They clearly state which plugin or default agent is handling the task and include the reasoning behind the selection.