vibekit

Original：🇺🇸 English

Translated

Ticket-driven development workflow for AI coding agents using VibeKit CLI. Use when the user asks to create a task, feature, bug fix, or ticket; mentions "vibe new", "vibe list", or vibekit commands; or wants structured, scoped work breakdown. Triggers on phrases like "add a ticket", "track this task", "break this down", or "start a new feature". Helps agents create focused tickets with clear acceptance criteria before writing code.

2installs

Sourcevibedx/vibekit

Added on2026-04-11

NPX Install

npx skill4agent add vibedx/vibekit vibekit

SKILL.md Content

View Translation Comparison →

VibeKit — Ticket-Driven Development

VibeKit is a CLI for managing development tickets and AI-assisted workflows. This skill teaches agents how to use vibekit properly — create tickets before coding, work through them systematically, and keep tickets as living documentation.

🔴 MANDATORY RULE: Always Create a Ticket First

Before writing ANY code on a repo that has a
.vibe/
directory, you MUST create a vibekit ticket. No exceptions for features, bug fixes, refactors, or multi-step tasks.

This is not a suggestion — it's the core workflow. If the user asks you to "add X", "fix Y", or "build Z", your first action should be:

bash

vibe new "descriptive title" --assignee <your-username> --priority <level> -n

Then read the ticket, plan the work, and

vibe start TKT-XXX

before touching any code.

Only skip the ticket for truly trivial changes: typo fixes, single-line config tweaks, or answering a quick question.

Why This Matters

Tickets break work into scoped, focused chunks that reduce AI drift and create documentation as a side effect. They also give humans a clear trail of what was done and why — critical for collaboration between humans and agents.

bash

# 1. Create a ticket
vibe new "Add user authentication" --assignee <username> --priority high -n

# 2. Start working (creates git branch feature/TKT-XXX-slug)
vibe start TKT-001

# 3. Implement the work, commit with ticket reference
git commit -m "TKT-001: add login endpoint"

# 4. Close when done
vibe close TKT-001

Installation

bash

npm install -g @vibedx/vibekit

Then in any project:

bash

vibe init          # Creates .vibe/ directory with config, team, templates

Core Commands

Command	Purpose
`vibe init`	Initialize vibekit in a project
`vibe new "title"`	Create a ticket
`vibe list`	List all tickets
`vibe start <id>`	Start work (creates git branch)
`vibe close <id>`	Mark ticket done
`vibe lint`	Validate ticket format
`vibe lint --fix`	Auto-fix missing sections
`vibe refine <id>`	AI-enhance ticket details
`vibe team`	Manage team members

Creating Tickets (for AI agents)

Always use
-n
/
--no-interactive
when creating tickets programmatically. This skips the AI enhancement prompt which would otherwise block automation.

bash

vibe new "Fix login redirect loop" --assignee alice --priority high -n
vibe new "Add dark mode" --assignee bob --author alice -n

Useful flags

```
--priority low|medium|high|critical
```
(default: medium)
```
--status open|in_progress|review|done
```
(default: open)
```
--assignee <username>
```
— who works on it
```
--author <username>
```
— who created it
```
-n
```
/
```
--no-interactive
```
— skip AI enhancement prompt

Ticket Structure

Tickets live in

.vibe/tickets/

as markdown files with YAML frontmatter:

markdown

---
id: TKT-001
title: Add user authentication
slug: TKT-001-add-user-authentication
status: open
priority: high
assignee: "alice"
author: "bob"
created_at: 2026-04-11T10:00:00Z
updated_at: 2026-04-11T10:00:00Z
---

## Description
What needs to be done and why.

## Acceptance Criteria
- [ ] Concrete checkbox 1
- [ ] Concrete checkbox 2

## Implementation Notes
Technical details, file paths, API references.

## Testing & Test Cases
Brief test scenarios.

Filtering Tickets

bash

vibe list                       # All tickets
vibe list --status=open         # Only open
vibe list --assignee=alice      # Only alice's tickets

Team Management

Teams are stored in

.vibe/team.yml

. Assignee values in tickets should match team member IDs.

bash

vibe team add alice --name "Alice" --github alice --slack U0ABC123 --role Engineer
vibe team                       # List members
vibe team show alice            # Show one member

When to Use This Skill

Apply vibekit workflow when:

User asks to "add a feature", "fix a bug", "implement X", "build Y"
Task is non-trivial (more than a one-line fix)
Work touches multiple files or requires planning
User mentions
```
vibe
```
, tickets, tracking, or task management
Working in a project that has a
```
.vibe/
```
directory

Don't force tickets for trivial changes — typo fixes, config tweaks, or single-line edits can skip the ticket workflow.

Integration with Git

vibe start TKT-001

automatically:

Creates branch
```
feature/TKT-001-<slug>
```
(or configured prefix)
Updates ticket status to
```
in_progress
```
Switches to the new branch

vibe close TKT-001

:

Updates ticket status to
```
done
```
Leaves the branch for manual merge/PR

Automation Pattern

For bots and automated agents working through tickets:

bash

# Find open tickets assigned to you
vibe list --assignee=mybotname --status=open

# For each ticket:
# 1. Read .vibe/tickets/TKT-XXX-*.md for full context
# 2. Do the work on branch opus/<ticket-id>-<description>
# 3. Commit changes
# 4. Close: vibe close TKT-XXX
# 5. Notify team

Links

Repo: https://github.com/vibedx/vibekit
npm: https://www.npmjs.com/package/@vibedx/vibekit
Issues: https://github.com/vibedx/vibekit/issues

vibekit

NPX Install

Tags

SKILL.md Content

VibeKit — Ticket-Driven Development

🔴 MANDATORY RULE: Always Create a Ticket First

Why This Matters

Installation

Core Commands

Creating Tickets (for AI agents)

Useful flags

Ticket Structure

Filtering Tickets

Team Management

When to Use This Skill

Integration with Git

Automation Pattern

Links