What problem does it solve?
Organize and dispatch user requests to the correct Autopus sub-workflow (e.g., setup, status, plan, go, fix, review, sync, idea, map, why, verify, secure, test, dev, canary, doctor) so complex automations load the right context and run the appropriate routine.
Core Features & Use Cases
- Thin router surface that delegates to specialized workflows: auto-setup, auto-status, auto-plan, auto-go, auto-fix, auto-review, auto-sync, auto-idea, auto-map, auto-why, auto-verify, auto-secure, auto-test, auto-dev, auto-canary, auto-doctor.
- Context-aware: resolves SPEC paths and loads project context files before execution to ensure correct scope.
- Flexible invocation: supports both @auto and $auto forms and automatically wires to the corresponding detailed surface.
Quick Start
Ask @auto to run plan for a SPEC and route execution to the appropriate detailed workflow surface.