Jira Ticket

Overview

Use this skill to turn a Jira ticket into an implementation workflow for this repository. Start from the ticket, gather evidence with Atlassian MCP, verify the codebase locally, route into the required repo skills, propose a concrete implementation plan via $dev plan, and after user agreement execute autonomously until blocked — then post-delivery Assure before reporting done.

Inputs

• Accept either a Jira URL or a Jira key such as ABC-123.
• Normalize the ticket key immediately and use it consistently in branch names, status updates, and handoff.

Hard Requirements

• Use Atlassian MCP. Do not rely on copied ticket text alone when Jira is accessible.
• Verify you are in the correct repository before planning or editing code.
• Read the local code before making claims. Scan files and contracts; do not assume architecture from the ticket wording.
• If the ticket or linked material cites APM / traces, error tracking, or logging links/IDs, use the matching observability MCP when available; fold findings into the assessment.
• Follow repository routing from AGENTS.md.