Trigger the full Autopus plan, go, and sync workflow with a single alias.
npx skills add https://github.com/shin0720/autopus --skill auto-dev-shin0720
Please help me install this Agent Skill. Skill: auto-dev Source: https://github.com/shin0720/autopus/tree/main/.autopus/plugins/auto/skills/auto-dev Command: npx skills add https://github.com/shin0720/autopus --skill auto-dev-shin0720
Running full Autopus development workflows requires manually executing separate plan, go, and sync commands in sequence, which adds unnecessary friction and risks flag mismatches between steps. This skill acts as a thin alias shim that triggers the entire end-to-end development cycle in a single invocation, preserving all user-specified flags exactly.
Use the auto-dev skill to run a full end-to-end development workflow for your current feature, preserving all your specified flags like --auto and --team.
High-intent search queries and answers about installing and using this skill.
You can run a full-cycle feature development workflow using a single alias command that triggers the entire end-to-end pipeline, eliminating the need to manually execute individual plan, build, and sync steps.
Automating an end-to-end dev workflow through a single alias preserves all custom flags like --auto and --team exactly as entered, ensuring team collaboration and automation parameters are maintained without modification across the pipeline.
An alias shim executes complete code automation pipelines by mapping a single command to the canonical router, delegating context loading and SPEC path resolution before triggering the full plan, go, and sync development cycle.
Yes, you can trigger the entire plan, go, and sync development cycle with one invocation by passing your feature description and workflow flags to the unified alias, which delegates execution to the canonical development router.
No, you do not need to manually resolve SPEC paths before starting an automated feature development pipeline because the alias delegates context loading and SPEC path resolution automatically to the canonical router during execution.
Running separate development workflow commands adds friction and risks flag mismatches because manual sequential execution requires repeated parameter entry, which the single alias approach solves by preserving all user-specified workflow flags exactly.
InsajinRoute user subcommand requests to the correct Autopus workflow surface.
windyskyOrchestrate SPEC workflows with EARS format and Plan-Run-Sync lifecycle.
moogieonAnalyze commit history and code quality metrics for weekly engineering retrospectives.
HeadyAIChain tools, services, and AI agents into deterministic pipelines across MCP tools.
