Work on Ticket

Start work on a Jira ticket by fetching ticket details, making sure my jujutsu state is setup, and doing some initial research.

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"
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 Zapier MCP tool to fetch the ticket:

zapier-mcp_execute_search_action({
  app: "jira",
  action: "issue_jql",
  instructions: "Find ticket [TICKET_ID]",
  output: "Return the issue key, summary, description, issue type, priority, and status",
  params: {
    jql: "key = [TICKET_ID]",
    fields: "summary,description,issuetype,priority,status"
  }
})

Extract from response:

Summary (title)
Description
Issue type
Status
Any other relevant context

3. Generate Jujutsu Bookmark Name

Create a bookmark name using this format:

[TICKET_ID]-[kebab-case-summary]

Bookmark Naming Rules:

All lowercase, kebab-case, max 50 chars
Start with the ticket ID (e.g., agp-782-)
Convert summary to kebab-case (lowercase, dashes instead of spaces)
Remove special characters
Use meaningful words

Examples:

agp-782-migrate-existing-mcp-server
aicc-123-fix-auth-token-expiry
proj-456-add-user-settings-page

Commit Message Rules:

All lowercase
No ticket ID in the message
Short and descriptive (max 50 chars)
Example: 'migrate mcp server to new architecture'

4. Prepare Or Reuse The Jujutsu State

Check the current state and bookmarks:

jj st
jj bookmark list

If the expected ticket bookmark already points to @, the workspace skill prepared this checkout. Reuse it and skip the fetch, jj new, description, and bookmark commands below. Continue with task planning in the current workspace.

Otherwise, create the ticket change from current main:

# Ensure we're on the latest main
jj git fetch --remote origin --branch main
jj new 'main@origin' # create a new commit on top of current GitLab main

# Create bookmark with description
jj describe -m 'lowercase short description, no ticket id, max 50 chars'
jj bookmark create [BOOKMARK_NAME]

Confirm to James: "Described and bookmarked [BOOKMARK_NAME]"

6. Build Task Planning Prompt

Analyze the Jira ticket and create a comprehensive prompt for the /investigate command:

Prompt should include:

The ticket summary
Key details from the description
Any acceptance criteria mentioned
Relevant technical context

Example prompt construction:

Summary: [ticket.summary]

Description: [ticket.description]

Acceptance Criteria:
[extracted criteria if present]

7. Execute Task Planning

Run the /investigate slash command with the ticket number and constructed prompt:

/investigate [TICKET_ID] [CONSTRUCTED_PROMPT]

Example:

/investigate AGP-782 Migrate existing MCP server implementation to new architecture

Description: We need to refactor the MCP server to use the new modular architecture. This includes updating the tool registry, migrating existing tools, and ensuring backward compatibility.

Acceptance Criteria:
- All existing tools work with new architecture
- Tests pass
- No breaking changes to API

Example Usage

Example 1: Simple Ticket

User: "work on AGP-782"

Claude:

Fetches AGP-782 from Jira
Finds summary: "Migrate existing MCP server"
Checks jj state, creates new commit off main
Creates bookmark and describes: agp-782-migrate-existing-mcp-server
Runs: /investigate AGP-782 Migrate existing MCP server implementation...

Example 3: Ticket Not Found

User: "work on BAD-999"