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:

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