๐2 AM. Production is Down.
Backend removed an endpoint. Frontend didn't know. Tests passed. Production broke.
Sound familiar? Drift between specs, code, tests, and docs causes:
- ๐ฅ Integration bugs in production
- ๐ Outdated documentation
- ๐งช Missing test coverage
- โฐ Wasted developer time
- ๐ฐ 3 AM debugging sessions
โจ Find Out in Development. Not at 2 AM.
SpecSync validates alignment at commit-time. It blocks commits with drift and tells you exactly what to fix.
No drift in git = No drift in production.
โจ Key Features
Automatic Detection
Detects drift between specs, code, tests, and docs on every commit
Task Generation
Generates specific, actionable tasks to fix each issue
Steering Rules
Customize validation behavior with project-specific rules
Three Modes
Blocking, task generation, or auto-fix - choose what works for you
๐ Quick Start
# Install SpecSync Bridge
pip install specsync-bridge
# Interactive setup wizard
specsync-bridge setup
โ Auto-detected role: consumer
โ Configured dependencies
โ Auto-sync enabled
# Make a change and commit
git add backend/handlers/user.py
git commit -m "Add user endpoint"
โ Drift Detected - Commit Blocked
- No spec for endpoint
- No tests for endpoint
- No docs for endpoint
# Fix and commit again
git add .kiro/specs/ tests/ docs/
git commit -m "Add endpoint with spec, tests, docs"
โ Commit successful - All aligned!