auto-dev

Routing alias-based development requests to a canonical workflow router involves using a thin alias shim that reinterprets incoming calls and forwards them to the main router. This approach preserves intent and supports all router flags.

SPEC path resolution in full-cycle development management is the process of resolving specification file paths during context loading. It is an orchestration step performed before invoking a detailed workflow to ensure correct handoff and environment setup.

Yes, the auto skill must be present to use the auto-dev alias. The alias shim depends on the canonical auto router to load the detailed development workflow and execute the required context load operations.

To load a detailed development workflow across environments, invoke the alias using the standard command syntax with your arguments. The shim reinterprets the call as the canonical payload and forwards it to the main router for processing.

Yes, you can pass all router flags and subcommands through the alias shim during workflow handoff. The shim is designed to support the full set of flags claimed by the main router, ensuring flexible routing and preservation of intent.

An auto-dev invocation fails to load the detailed workflow process if the required auto skill is not present in the environment. The alias requires this canonical router dependency to perform context load and SPEC path resolution successfully.