▄▀█ █ █ ▀█▀ █▀█ █▀ █▀█ █▀▀ █▀▀ █▀█ █▄█ █ █▄█ ▄█ █▀▀ ██▄ █▄▄
Spec-Driven Development Automation
Stop AI slop. Build features systematically with AI-powered specification workflows.
What is autospec?
autospec brings structure to AI coding: spec → plan → tasks → implement - all in one command.
Built for CLI coding agents including Claude Code, Codex, and OpenCode, and inspired by GitHub SpecKit, autospec reimagines the specification workflow with YAML-first artifacts for programmatic access and validation.
Supported agents: Claude Code, Codex CLI, and OpenCode.
# Generate everything: spec → plan → tasks → implement
autospec run -a "Add user authentication with OAuth"
# Or step by step with review between stages
autospec run -s "Add feature" # Generate spec
# Review and edit spec.yaml
autospec run -pti # Plan, tasks, implement
Creates specs/<feature-name>/ with YAML artifacts at each stage:
| Stage | Creates | Contents |
|---|---|---|
| specify | spec.yaml |
Requirements, acceptance criteria |
| plan | plan.yaml |
Architecture, design decisions |
| tasks | tasks.yaml |
Ordered tasks with dependencies |
| implement | Updates tasks.yaml |
Task status, completion |
Key Features
Automated Workflow Orchestration
Runs stages in dependency order with automatic retry on failure. No manual intervention needed.
YAML-First Artifacts
Machine-readable spec.yaml, plan.yaml, tasks.yaml for programmatic access and validation.
Smart Validation
Validates artifacts exist and meet completeness criteria before proceeding to the next stage.
Session Isolation
Per-phase or per-task execution reduces API costs by 80%+ on large specs through context isolation.
Quick Start
Prerequisites
- Claude Code, Codex CLI, or OpenCode installed and configured
- Git
Installation
curl -fsSL https://raw.githubusercontent.com/ariel-frischer/autospec/main/install.sh | sh
First Workflow
# Navigate to your project
cd your-project
# Check dependencies
autospec doctor
# Initialize autospec configuration (prompts to create constitution)
autospec init
# Create your first specification (also runs git checkout for feature branch)
autospec run -s "Add user authentication with OAuth"
The Workflow
autospec runs four core stages in sequence:
| Stage | Command | Creates | Description |
|---|---|---|---|
| specify | autospec specify "desc" |
spec.yaml |
Feature specification with requirements |
| plan | autospec plan |
plan.yaml |
Implementation design and architecture |
| tasks | autospec tasks |
tasks.yaml |
Actionable task breakdown with dependencies |
| implement | autospec implement |
— | Executes tasks, updates status |
Each artifact is validated before proceeding to the next stage, ensuring quality at every step.
Documentation
| Section | Description |
|---|---|
| Quickstart | Get up and running in 5 minutes |
| Reference | Complete CLI command reference |
| Guides | Configuration, troubleshooting, FAQ |
| FAQ | Common workflow and agent questions |
What Makes autospec Different?
| Feature | GitHub SpecKit | autospec |
|---|---|---|
| Output Format | Markdown | YAML (machine-readable) |
| Workflow UX | Repetitive, non-composable command flow | One-command end-to-end runs (autospec run -a, autospec prep) |
| Validation | Checklist/agent-driven review | Programmatic validation with retry logic |
| Token Efficiency | Long implementation chats can accumulate large context | Fresh bounded sessions per phase/task (80%+ cost savings) |
| Status Visibility | No built-in core status command | Built-in phase/task progress via autospec st |
| Phase Orchestration | Agent-driven /speckit.* commands |
CLI-orchestrated stages with dependency handling |
| Workflow Engine | Prompt files + shell/PowerShell helpers | Typed Go orchestration in a single binary |
License
autospec is distributed under the MIT License.