Loading...
Loading...
Found 258 Skills
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.
Takes meeting transcripts, extracts action items with owners and deadlines, detects implicit commitments, generates structured meeting summaries, and outputs task files compatible with Linear, GitHub Issues, and other project management tools.
Executes project delivery in five phases (analysis, planning, implementation, validation, delivery) with checklists and a structured final report. Use when the user asks to execute a phase, deliver Phase 1, run a methodological delivery, or follow phased execution.
Analyze a GitHub issue and create a detailed technical specification
Lane integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lane data.
Celoxis integration. Manage data, records, and automate workflows. Use when the user wants to interact with Celoxis data.
Creates a comprehensive pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness. Use before releasing features, products, or major updates to ensure nothing is missed.
Create an implementation plan artifact in Aiden
Turn a GitHub issue into an implementation plan — investigate the codebase, propose an approach, list critical files and changes, outline test strategy. Use when user says 'plan this issue', 'what's the approach for', 'how would I tackle', 'implementation plan for', or 'before coding'. Do NOT use for actually implementing (write the code directly after the plan) or for breaking a too-large issue into sub-issues (use splice-issue).
To do / In progress / In review / Done 四列, 卡片 + 头像 + 泳道
Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.
Vendor-neutral skill to generate a release risk checklist from scope, dependencies, and rollout constraints.