What problem does it solve? It removes the context-switching between your editor and Jira by letting you view issues, create branches from tickets, transition statuses, and create new tickets directly through the Atlassian MCP integration. ## Core Features & Use Cases - Issue Viewing: Fetch and format Jira issue details (status, assignee, priority, description) from a bare key like OK-51513 or a full Atlassian URL. - Branch Generation: Map issue types to branch prefixes (Bug → fix, Story → feat), generate slugs from summaries, and detect local/remote branch collisions before creating the branch. - Status Transitions & Ticket Creation: Match workflow events (start_work, pr_opened, pr_merged) to available Jira transitions, and create new tickets with markdown descriptions validated against project issue types. - Use Case: You are assigned ticket OK-51513. Run the branch subcommand to get feat/OK-51513-add-user-profile-page, then transition the ticket to In Progress with a single event command when you start work. ## Quick Start Ask the assistant to view Jira ticket OK-51513 and create a branch for it using the jira skill.