jira-ticket-start

What problem does it solve?

Developers waste time onboarding Jira tickets: hunting for ticket context, creating correctly named branches, and starting a focused codebase investigation. This Skill centralizes ticket details, enforces branch naming conventions, and produces an initial investigation and complexity assessment so engineers can begin implementation with full context.

Core Features & Use Cases

• Fetch ticket details from Atlassian MCP including summary, description, acceptance criteria, status, and priority.
• Create feature branches that follow repository conventions and ensure work happens on the correct base (pull main first).
• Kick off investigation by locating related files, identifying integration points, and estimating LOC-based complexity (Simple/Medium/Complex).
• Transition ticket status to In Progress when appropriate and produce an actionable output: ticket summary, branch name, investigation findings, and recommended next steps.
• Use case: A developer picks up PROJ-123 and uses the Skill to fetch details, create feat/add-tooltip-PROJ-123, surface related components, and determine if a multi-step plan is needed.

Quick Start

Start work on PROJ-123 by running the jira-ticket-start skill with the ticket ID to fetch details, create the correctly named branch, and produce an investigation summary.