work-on-ticketlisted

# Work on Ticket Streamlined workflow to start work on a Jira ticket by fetching ticket details, creating a branch, and initiating task planning. ## When to Use This Skill Activate this skill when: - The user says "work on AGP-123" or "start work on AGP-123" - The user says "pick up AGP-123" or "begin AGP-123" - The user mentions starting work on a specific Jira ticket ID - Pattern: `work on [TICKET_ID]` or similar intent ## Workflow ### 1. Parse Ticket ID Extract the Jira ticket ID from the user's message. Common patterns: - `work on AGP-782` - `start AGP-782` - `pick up PROJ-123` Ticket ID format: `[A-Z]+-[0-9]+` (e.g., AGP-782, AICC-123) ### 2. Fetch Jira Ticket Details Use the MCP Zapier tool to fetch the ticket: ```typescript mcp__zapier - frontend__jira_software_cloud_find_issue_by_key({ instructions: "Get details for ticket [TICKET_ID]", key: "[TICKET_ID]", fields: "summary,description,issuetype,priority,status", }); ``` **Extract from response:** - Summary (title) - Description - Issue type - Status - Any other relevant context ### 3. Generate Branch Name Create a branch name using this format: ``` [TICKET_ID]-[kebab-case-summary] ``` **Branch Naming Rules:** - Start with the ticket ID (e.g., `AGP-782-`) - Convert summary to kebab-case (lowercase, dashes instead of spaces) - Remove special characters - Keep it concise (max 50 characters total) - Use meaningful words from the summary **Examples:** - `AGP-782-migrate-existing-mcp-ser