━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
██╗ ██╗██╗██████╗ ███████╗███████╗██████╗ ███████╗ ██████╗
██║ ██║██║██╔══██╗██╔════╝██╔════╝██╔══██╗██╔════╝██╔════╝
██║ ██║██║██████╔╝█████╗ ███████╗██████╔╝█████╗ ██║
╚██╗ ██╔╝██║██╔══██╗██╔══╝ ╚════██║██╔═══╝ ██╔══╝ ██║
╚████╔╝ ██║██████╔╝███████╗███████║██║ ███████╗╚██████╗
╚═══╝ ╚═╝╚═════╝ ╚══════╝╚══════╝╚═╝ ╚══════╝ ╚═════╝
S P E C S - F I R S T D E V E L O P M E N T
F O R C L A U D E C O D E
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Transform your development process with enforced planning before implementation
Getting Started · Documentation · Examples · Contributing
Option 1: One-Command Install (Recommended)
curl -sSL https://raw.githubusercontent.com/frankekn/vibespec/main/remote-install.sh | bashOption 2: Git Clone Install
git clone https://github.com/frankekn/vibespec.git
cd vibespec
./install.sh /path/to/your/projectOption 3: Manual Install
cp vibespec/{WORKFLOW.md,workflow-rules.md} your-project/
cp -r vibespec/.claude your-project/- Enforces specs-first development workflow for Claude Code
- Appends workflow rules to your existing CLAUDE.md (non-destructive)
- Adds WORKFLOW.md with the complete 6-step process
- Installs hooks that BLOCK coding without approved specs
- Creates specs/ directory for your requirements and designs
- Ensures Claude cannot skip workflow steps
- Understand - Clarify requirements with the user
- Requirements - Document in EARS format (
specs/{feature}/requirements.md) - Design - Technical approach (
specs/{feature}/design.md) - Tasks - Implementation plan (
specs/{feature}/tasks.md) - Code - Implementation following the specs
- Update - Keep documentation current
After installation, Claude MUST follow this enforced pattern:
You: "Add user authentication"
Claude: "I'll help you add user authentication. Following the Vibespec workflow,
let me first understand your requirements:
- What type of authentication? (JWT, OAuth, etc.)
- What are the user roles?
- Any specific security requirements?
After clarifying, I'll create specs/user-authentication/requirements.md
⏳ I will then WAIT for your approval before proceeding to design.md"
Key Enforcement Points:
- Claude CANNOT skip to coding without creating specs
- Claude MUST wait for approval between each step
- Hooks BLOCK actions that violate the workflow
- All 3 spec files (requirements/design/tasks) are REQUIRED before coding
If you already have a CLAUDE.md file, Vibespec will:
- Append workflow rules with clear section markers
- Preserve all your existing instructions
- Add rules that work alongside your current setup
your-project/
├── CLAUDE.md # Your existing + Vibespec rules
├── WORKFLOW.md # Detailed process documentation
├── specs/ # Feature specifications
└── .claude/ # Hooks configuration
├── settings.json # Hook definitions
└── hooks/ # Enforcement scripts
After installation, try these commands:
- "I want to add a search feature" → ENFORCED: Creates specs first
- "Just quickly add a button" → ENFORCED: Still creates minimal specs
- "Implement the login from specs" → ENFORCED: Only works with approved specs
- "Emergency bypass for critical bug" → ALLOWED: Bypasses workflow
What happens if you try to skip workflow:
You: "Just add some code to fix this"
Claude: 🛑 VIBESPEC WORKFLOW ENFORCEMENT
❌ Cannot proceed without following specs-first workflow!- Getting Started - Detailed setup guide
- WORKFLOW.md - Complete workflow documentation
- Hooks Guide - Understanding the enforcement system
- Customization - Adapting to your needs
- ✅ macOS: Fully supported
- ✅ Linux: Fully supported
⚠️ Windows: Requires WSL or Git Bash (bash scripts only)
- One-command install: < 30 seconds
- First feature spec: < 5 minutes
- Learning curve: Works immediately, no manual required
- Enforcement: Automatic, no configuration needed
We welcome contributions! Please follow the Vibespec workflow when adding features to Vibespec itself.
MIT License - see LICENSE file
Frank Yang
Email: vibespecs@gmail.com
Made with ❤️ for the Claude Code community
Inspired by Amazon's Kiro IDE