[FEATURE] - Add developer-kit-jira plugin with Atlassian MCP Server integration

[giuseppe-trisciuoglio]

Summary

Implements #46 - Jira support for the developer-kit with full Git-Jira workflow integration using the official Atlassian MCP Server.

Changes

New Plugin: developer-kit-jira

• Skill: jira-mcp-workflow - Comprehensive workflow management with MCP integration
• 10 Commands organized in two categories:

Ticket Management Commands

• devkit.jira.ticket.view - View Jira ticket details
• devkit.jira.ticket.comment - Add comments to tickets
• devkit.jira.ticket.transition - Manage ticket status transitions

Workflow Commands

• devkit.jira.workflow.start - Start development on a ticket (branch creation + Jira update)
• devkit.jira.workflow.commit - Commit with Jira reference + add comment
• devkit.jira.workflow.push - Push branch + update Jira
• devkit.jira.workflow.pr-create - Create PR + transition to "In Review"
• devkit.jira.workflow.pr-ready - Mark PR ready + transition to "Reviewing"
• devkit.jira.workflow.pr-merge - Merge PR + transition to "Done"
• devkit.jira.workflow.status - Show combined git and Jira status

Key Features

• Automatic ticket inference from branch names (feature/PROJECT-123)
• Atlassian MCP Server integration for all Jira operations
• User confirmations before all state changes
• Git-Jira synchronization for complete SDLC workflow
• Input validation with regex pattern [A-Z]+-[0-9]+
• Branch name sanitization to prevent injection

Security

• No hardcoded credentials
• Uses OAuth 2.1 (3LO) via Atlassian MCP Server
• Tool restrictions: Bash(git *), Bash(gh *)
• All destructive operations require confirmation

Prerequisites

Users need to configure the Atlassian MCP Server in their .mcp.json:

{
  "mcpServers": {
    "atlassian": {
      "type": "http",
      "url": "https://mcp.atlassian.com/v1/mcp"
    }
  }
}

Testing

• All 194 files pass validation
• Security review completed (no vulnerabilities found)
• Component review passed

Checklist

• Code follows project style guidelines
• No breaking changes
• Plugin structure follows conventions
• Commands have proper tool restrictions
• Skill includes all required sections

Closes #46