jira

Use this agent when the main agent needs to perform Jira operations in an isolated context — pulling ticket context, updating ticket progress, decomposing specs into tickets, or working a ticket end-to-end. Examples: <example> Context: User wants full context on a ticket user: "Pull up PROJ-123 with all the details" assistant: "I'll use the jira-agent to pull the full ticket context." <commentary> Full ticket context request triggers jira-agent delegation. </commentary> </example> <example> Context: User wants to update a ticket's status with context user: "Mark PROJ-456 as done — we shipped the API changes" assistant: "I'll use the jira-agent to update that ticket." <commentary> Stage-based progress update triggers jira-agent delegation. </commentary> </example> <example> Context: User wants to create tickets from a spec user: "Break down the auth redesign spec into Jira tickets" assistant: "I'll use the jira-agent to decompose that spec into tickets." <commentary> Spec decomposition triggers jira-agent delegation. </commentary> </example> <example> Context: User wants the agent to work a ticket user: "Pick up PROJ-789 and start working on it" assistant: "I'll use the jira-agent to claim and work that ticket." <commentary> Ticket-driven work triggers jira-agent delegation. </commentary> </example>

Use when needing to understand a Jira ticket before acting on it — pulling context for an agent, reviewing a ticket's full picture, loading ticket details for decision-making, or when asked to "show me" or "what's in" a ticket.

Use when the user has a spec, architecture doc, implementation plan, or feature description and wants to break it into Jira tickets for distribution to people or agents. Also triggered by "create tickets from this plan" or "file tickets for this spec".

Use when work on a ticket has reached a stage boundary — started working, sent for review, completed, blocked, or reopened. Handles status transition, comment, and field updates in one pass.

Use when the user assigns a ticket to the agent, says "work on this ticket", "pick up this item", or wants the agent to claim a ticket and execute against it. Procedural harness that wraps any work with Jira discipline.

Use when a project's workflow statuses need to be configured for the first time, or refreshed. Triggered automatically by jira-progress when a project is missing from config/workflows.json, or manually via "configure workflow", "set up statuses for X", "refresh workflow for X".

1 hook across 1 event