lev

Natural language command routing maps user aliases to stable primitives like get, work, ask, check, and go. The router parses intent, resolves protocol URIs like lev:// or skill://, and dispatches commands to the appropriate specialist skills.

To route commands to specialist skills, execute the unified entry point command. It parses the input intent, matches it to specific lifecycle stages and primitives, and seamlessly directs the request to the correct sub-skill for execution.

Yes, you can use protocol URIs to dispatch tasks. The router resolves various URI schemes including lev://, skill://, flowmind://, and workshop:// to facilitate seamless protocol routing and integration across the ecosystem.

The best way to manage CLI lifecycle stages is through an intelligent routing entry point. It abstracts complex interactions by parsing natural language intent and automatically mapping requests to the correct lifecycle primitives.

No external dependencies are required to handle protocol routing and intent dispatch. The skill operates as a self-contained master router, managing protocol resolution and primitive mapping natively without additional environment setup.

If a natural language alias is not resolving to the correct specialist skill, the intent parser may fail to map the input to stable primitives like get or work, or the specified protocol URI might be unsupported by the router.