| Crates.io | vibe-ticket |
| lib.rs | vibe-ticket |
| version | 0.4.0 |
| created_at | 2025-07-21 15:47:48.959787+00 |
| updated_at | 2025-11-25 10:01:14.501249+00 |
| description | A high-performance ticket management system for Vibe Coding environment |
| homepage | |
| repository | https://github.com/nwiizo/vibe-ticket |
| max_upload_size | |
| id | 1762196 |
| size | 1,132,563 |
A high-performance ticket management system for developers, built with Rust. Features Git worktree integration for parallel development workflows.
# Install
cargo install vibe-ticket
# Initialize project
vibe-ticket init
# Create and start a ticket
vibe-ticket new fix-bug --title "Fix login issue" --priority high
vibe-ticket start fix-bug # Creates Git worktree by default
# Work in the worktree
cd ./my-project-vibeticket-fix-bug/
# Track progress
vibe-ticket task add "Fix null check"
vibe-ticket task complete 1
# Complete ticket
vibe-ticket close fix-bug --message "Fixed login issue"
# Create specification from natural language
vibe-ticket spec specify "Build a REST API for user management"
# Generate implementation plan
vibe-ticket spec plan --tech-stack rust,actix-web
# Create tasks and export as tickets
vibe-ticket spec tasks --parallel --export-tickets
# Start working on generated tickets
vibe-ticket list --open
vibe-ticket start api-t001-initialize
/specify/plan/tasks/validateTransform natural language requirements into executable specifications:
# Create specification from requirements
vibe-ticket spec specify "Build a REST API for user management"
# Generate implementation plan
vibe-ticket spec plan --tech-stack rust,actix-web --architecture microservices
# Create executable task list
vibe-ticket spec tasks --granularity fine --parallel --export-tickets
# Validate specification
vibe-ticket spec validate --check-ambiguities --generate-report
When using Claude Code with MCP integration:
/specify "Build a REST API with authentication"
/plan --tech-stack rust,postgresql
/tasks --parallel --export-tickets
/validate --generate-report
vibe-ticket --help # Show help for any command
vibe-ticket check # Check current status
vibe-ticket list --open # Show active tickets
vibe-ticket search "keyword" # Search tickets
vibe-ticket worktree list # List all worktrees
vibe-ticket spec list # List all specifications
# Update multiple tickets at once
vibe-ticket bulk update --status doing --priority high tag1,tag2
# Tag multiple tickets
vibe-ticket bulk tag "important,urgent" ticket1 ticket2 ticket3
# Close multiple tickets
vibe-ticket bulk close ticket1 ticket2 --message "Batch close"
# Archive old tickets
vibe-ticket bulk archive --before 2024-01-01
# Create a reusable filter
vibe-ticket filter create urgent-bugs --status todo --priority high --tags bug
# List saved filters
vibe-ticket filter list
# Apply a filter
vibe-ticket filter apply urgent-bugs
# Create command shortcuts
vibe-ticket alias create today "list --status doing"
vibe-ticket alias create urgent "list --priority high --priority critical"
# Run an alias
vibe-ticket alias run today
# Start/stop timer
vibe-ticket time start my-ticket
vibe-ticket time stop
# Log time manually
vibe-ticket time log my-ticket 2h30m --description "Implemented feature"
# View time report
vibe-ticket time report --period week
vibe-ticket time status
# Create lifecycle hooks
vibe-ticket hook create notify-slack post-close \
--command 'curl -X POST $SLACK_WEBHOOK -d "{\"text\": \"Ticket $TICKET_SLUG closed\"}"' \
--description "Notify Slack on ticket close"
# List and manage hooks
vibe-ticket hook list
vibe-ticket hook enable notify-slack
vibe-ticket hook test notify-slack
# Fuzzy search and select a ticket
vibe-ticket interactive select
# Multi-select for bulk operations
vibe-ticket interactive multi --status todo
# Quick status/priority change
vibe-ticket interactive status my-ticket
vibe-ticket interactive priority my-ticket
# .vibe-ticket/config.yaml
git:
worktree_default: true # Create worktrees by default
worktree_prefix: "./{project}-vibeticket-"
project:
default_priority: medium
# Generate CLAUDE.md for AI assistance
vibe-ticket init --claude-md
# Add strict AI rules
curl https://raw.githubusercontent.com/nwiizo/vibe-ticket/main/rules/agent.md >> CLAUDE.md
vibe-ticket can run as an MCP server for AI assistants like Claude:
# Install (MCP is now included by default)
cargo install vibe-ticket
# Add to Claude Code (global)
claude mcp add vibe-ticket ls $HOME/.cargo/bin/vibe-ticket --scope local -- mcp serve
# Test the server
vibe-ticket mcp serve
When using vibe-ticket with AI assistants via MCP:
/specify, /plan, /tasks, /validateExample AI interactions:
"Create a ticket for the bug we just found"
"Generate a specification for a REST API"
"/specify Build a user authentication system"
"/plan --tech-stack rust,jwt --architecture layered"
"/tasks --granularity fine --parallel"
"Validate the specification and check for ambiguities"
Available MCP Tools for Spec-Driven Development:
vibe-ticket_spec_specify - Create specs from natural languagevibe-ticket_spec_plan - Generate implementation plansvibe-ticket_spec_generate_tasks - Create task listsvibe-ticket_spec_validate - Validate specificationsSee MCP Integration Guide for detailed setup and usage.
./project-vibeticket-<slug>/ directoriesvibe-ticket worktree remove <ticket>vibe-ticket worktree list to track active worktreescargo test --doc regularly to ensure examples workvibe-ticket checkvibe-ticket list --status doing to see active workgit clone https://github.com/nwiizo/vibe-ticket.git
cd vibe-ticket
cargo build --release
cargo install --path .
# With MCP support
cargo build --release --features mcp
cargo install --path . --features mcp
See CONTRIBUTING.md for guidelines.