auto-dev

Automate end-to-end development workflows from requirements to code delivery.

1|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/wonder-zhang/openspec-autodev --skill auto-dev-wonder-zhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-dev
Source: https://github.com/wonder-zhang/openspec-autodev/tree/main/skills/auto-dev
Command: npx skills add https://github.com/wonder-zhang/openspec-autodev --skill auto-dev-wonder-zhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end development workflow from requirements clarification to code delivery using a multi-agent parallel-batch orchestration, enabling hands-off progress with a single human checkpoint.

Core Features & Use Cases

  • Automates the OpenSpec + Superpowers development workflow from planning to delivery with minimal human intervention.
  • Supports multiple sub-agents running in parallel batches, remote coordination when needed, and a TDD-driven cycle with continuous verification.
  • Provides session-based state management, environment setup, and automated validation and reporting to recover gracefully from interruptions.

Quick Start

Run the automation by initializing the project and starting the feature workflow with a single command

Frequently Asked Questions about auto-dev

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

FAQPage Schema
How do I automate the end-to-end development workflow from requirements to code delivery?

You can automate the end-to-end development workflow using multi-agent parallel-batch orchestration. This approach manages phases from requirements clarification to delivery with a single human checkpoint, enabling hands-off progress while running simultaneous sub-agents.

How does multi-agent parallel-batch orchestration work for feature development?

Multi-agent parallel-batch orchestration works by running simultaneous sub-agents across development phases. It coordinates remote teams, applies TDD-driven cycles with continuous verification, and uses session-based state management to recover gracefully from interruptions.

Can I run non-interactive TDD cycles with automated verification across multiple projects?

Yes, you can run non-interactive TDD cycles with automated verification across multiple projects. The workflow supports phase-based automation, environment setup, file-claim coordination, and session management to handle parallel execution and remote coordination.

What is the best way to manage automated dev-ops sessions and recover from interruptions?

The best way to manage automated dev-ops sessions is through session-based state management with automated validation and reporting. This mechanism tracks parallel-batch progress and handles environment setup, ensuring graceful recovery when interruptions occur during feature development.

Do I need a specific environment setup to coordinate parallel sub-agents for feature development?

You need an environment setup that supports non-interactive execution and file-claim coordination to coordinate parallel sub-agents. The workflow requires initializing the project and starting the feature workflow with a single command to trigger the automated pipeline.

Why does automated workflow require a single human checkpoint during parallel batch execution?

Automated workflow requires a single human checkpoint to validate requirements clarification and verify delivery readiness. This minimizes human intervention while ensuring the multi-agent parallel-batch orchestration, TDD cycles, and remote coordination align with project specifications.