auto-plan

Route plan requests to the canonical auto workflow while preserving flags.

106|74|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Insajin/autopus-adk --skill auto-plan-insajin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-plan
Source: https://github.com/Insajin/autopus-adk/tree/main/.autopus/plugins/auto/skills/auto-plan
Command: npx skills add https://github.com/Insajin/autopus-adk --skill auto-plan-insajin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thin alias shim routing plan commands to the canonical auto workflow, ensuring consistent behavior across plan invocations.

Core Features & Use Cases

  • Forwards plan invocations to the main auto workflow
  • Preserves and forwards flags such as --auto, --loop, --multi, --quality, --model, --variant, and --team
  • Performs Context Load and SPEC Path Resolution before handing off to the detailed workflow

Quick Start

Invoke the $auto-plan alias to route a plan request through the canonical auto workflow.

Frequently Asked Questions about auto-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route plan commands to an automated workflow using an alias?

To route plan commands to an automated workflow, you can invoke the $auto-plan alias to trigger the planning workflow and ensure flags are preserved for the detailed workflow.

What is an alias shim for routing automation workflows?

An alias shim for routing automation workflows is a thin layer that interprets alias form inputs and forwards plan invocations to the canonical auto router, ensuring consistent behavior across plan invocations.

Can I pass workflow flags like --auto or --model when using command-handling aliases?

Yes, you can pass workflow flags when using command-handling aliases. The routing shim preserves and forwards flags such as --auto, --loop, --multi, --quality, --model, --variant, and --team to the main workflow.

Do I need the auto skill installed to use the auto-plan command alias?

Yes, you need the auto skill installed to use the auto-plan command alias. The routing shim relies on the existence of the auto skill and the detailed workflows to hand off the plan request successfully.

What does the SPEC Path Resolution step do before handing off to the detailed workflow?

The SPEC Path Resolution step resolves the specification path before handing off to the detailed workflow. It performs Context Load and SPEC Path Resolution to prepare the routing of plan requests to the canonical auto router.

Why are my plan invocations not triggering the detailed auto workflow?

If your plan invocations are not triggering the detailed auto workflow, the routing shim may be failing to perform Context Load or SPEC Path Resolution, or the required auto skill dependency is missing from your environment.