workBenches supports two popular spec-driven development frameworks: spec-kit (GitHub) and OpenSpec (Fission AI).
Spec-driven development helps align humans and AI coding assistants by defining what to build before any code is written. This approach:
- 📋 Structures Planning - Clear requirements before coding
- 🤝 Aligns AI - Keep AI assistants on track
- 📝 Documents Intent - Living documentation that evolves
- 🔄 Enables Iteration - Review and adjust before implementation
Run the setup script and choose option 3:
./scripts/setup-workbenches.sh
# Select: 3) Install spec-driven development toolsThe setup script will:
- Check if spec-kit and OpenSpec are already installed
- Report version numbers for installed tools
- Offer to install missing tools
- Handle prerequisites (uv for spec-kit, npm for OpenSpec)
spec-kit (GitHub Spec Kit)
# Requires Python 3.11+ and uv package manager
uvx --from git+https://github.com/github/spec-kit.git specify init <project>OpenSpec
# Requires Node.js and npm
npm install -g @fission-ai/openspec@latest- Language: Python-based
- Best For: New projects (0→1)
- Installation: Via
uvx(Python package runner) - Prerequisites: Python 3.11+, uv package manager
- Command:
specify - Repository: https://github.com/github/spec-kit
Workflow:
/specify- Create specification/plan- Generate technical plan/tasks- Break into actionable tasks- Implement task by task
- Language: Node.js/TypeScript
- Best For: Existing projects (1→n), brownfield development
- Installation: Via npm
- Prerequisites: Node.js, npm
- Command:
openspec - Repository: https://github.com/Fission-AI/OpenSpec
- Website: https://openspec.dev/
Workflow:
- Proposal - Create change proposal with spec deltas
- Apply - Implement according to spec
- Archive - Merge approved changes into living specs
Key Features:
- Separates source of truth (
openspec/specs/) from proposals (openspec/changes/) - Tracks spec changes as diffs (ADDED, MODIFIED, REMOVED)
- Great for modifying existing behavior across multiple specs
Both tools work with popular AI coding assistants:
- Claude Code
- GitHub Copilot
- Cursor
- Windsurf
- Codex
- Cline
- And many more...
View installed tools and their versions:
./scripts/setup-workbenches.sh
# Dependencies and spec tools status shown automatically# Initialize a new project
specify init my-project
# In your AI assistant (e.g., Claude Code)
/specify # Create specification
/plan # Generate technical plan
/tasks # Break into tasks
# Then implement each task# Initialize in existing project
openspec init
# Create a change proposal
openspec list # See current changes
openspec validate <change-id> --strict # Validate proposal
openspec show <change-id> # Review details
# In your AI assistant
/openspec:proposal Add feature X
/openspec:apply
/openspec:archiveWithout Spec-Driven Development:
- Requirements scattered across chat history
- AI drifts from original intent
- Endless correction cycles
- Lost context between sessions
With Spec-Driven Development:
- Requirements captured in markdown files
- AI stays aligned with explicit specs
- Review intent before implementation
- Persistent context across sessions
- Easier collaboration and code review
- GitHub: https://github.com/github/spec-kit
- Blog Post: https://github.blog/ai-and-ml/generative-ai/spec-driven-development-with-ai-get-started-with-a-new-open-source-toolkit/
- GitHub: https://github.com/Fission-AI/OpenSpec
- Website: https://openspec.dev/
- Discord: https://discord.gg/YctCnvvshC
uv not found:
# Install uv manually
curl -LsSf https://astral.sh/uv/install.sh | sh
export PATH="$HOME/.local/bin:$PATH"Python version too old:
# Check Python version
python3 --version
# spec-kit requires Python 3.11+npm not found:
# Install Node.js and npm
# Ubuntu/Debian:
sudo apt update && sudo apt install nodejs npm
# macOS:
brew install node
# Or download from: https://nodejs.org/Permission errors:
# Use npm without sudo (recommended)
npm config set prefix ~/.npm-global
export PATH=~/.npm-global/bin:$PATH
# Then install OpenSpec
npm install -g @fission-ai/openspec@latestSpec-driven development tools complement workBenches' development workflow:
- Setup - Install tools via setup script
- Create Bench - Use
new-benchto create development environment - Initialize Spec Tool - Run
specify initoropenspec initin your project - Develop with AI - Use spec-driven workflow with AI assistants
- Create Projects - Use
onpto create new projects from benches
The tools are globally available once installed, so you can use them in any project on your system.