vibe-ticket
A high-performance ticket management system for developers, built with Rust. Features Git worktree integration for parallel development workflows.
Quick Start
# Install
# Initialize project
# Create and start a ticket
# Work in the worktree
# Track progress
# Complete ticket
Key Features
- Git Worktree Support: Work on multiple tickets simultaneously
- Concurrent Edit Protection: Safe multi-user/multi-process ticket access with automatic lock management
- Spec-Driven Development: Three-phase development with requirements, design, and tasks
- Task Management: Break tickets into trackable tasks
- Flexible Search: Find tickets with powerful filters
- Export/Import: JSON, YAML, CSV, and Markdown formats
- AI Integration: Claude Code support with CLAUDE.md generation
- MCP Server: Run as Model Context Protocol server for AI assistants
Essential Commands
Configuration
# .vibe-ticket/config.yaml
git:
worktree_default: true # Create worktrees by default
worktree_prefix: "./{project}-vibeticket-"
project:
default_priority: medium
Documentation
- Command Reference
- Configuration
- Spec-Driven Development
- Git Worktree Guide
- Claude Integration
- MCP Integration Guide
- Data Formats
AI Assistant Setup
# Generate CLAUDE.md for AI assistance
# Add strict AI rules
MCP (Model Context Protocol) Support
vibe-ticket can run as an MCP server for AI assistants like Claude:
# Install with MCP support
# Add to Claude Code (global)
# Test the server
See MCP Integration Guide for detailed setup and usage.
Best Practices
Ticket Management
- Always create a ticket before starting work
- Use meaningful ticket slugs that describe the task
- Update ticket status as work progresses
- Close tickets with descriptive completion messages
Git Worktree Workflow
- Each ticket gets its own isolated worktree directory
- Work in
./project-vibeticket-<slug>/directories - Clean up worktrees after closing tickets:
vibe-ticket worktree remove <ticket> - Use
vibe-ticket worktree listto track active worktrees
Documentation Testing
- Run
cargo test --docregularly to ensure examples work - Keep documentation examples up-to-date with code changes
- Doc tests prevent documentation drift
Active Development Tips
- Check current context with
vibe-ticket check - Use
vibe-ticket list --status doingto see active work - Break complex work into tasks within tickets
- Conduct retrospectives after major tasks
Concurrent Access Safety
- vibe-ticket automatically handles multiple users/processes accessing tickets
- File locking prevents data corruption during concurrent modifications
- Stale locks are automatically cleaned up after 30 seconds
- Operations retry automatically if a file is temporarily locked
Installation
From Source
# With MCP support
Prerequisites
- Rust 1.70+
- Git (for branch/worktree features)
Contributing
See CONTRIBUTING.md for guidelines.