read-jira.md

name	read-jira
description	Use when user says "read ticket XXX", "read XXX", or provides a Jira key matching pattern [A-Z]{1,6}-[0-9]{1,6} (e.g. FRONT-108, FEX-23). Fetches ticket context via acli before implementing or asking questions.

Read Jira Ticket

Overview

Fetch full Jira ticket context using acli before starting any implementation or asking clarifying questions. Ticket data is the source of truth for requirements, acceptance criteria, and scope.

Trigger

Activate when user input matches: ^[A-Z]{1,6}-[0-9]{1,6}(\.[0-9]{1,6})?$ — standalone or embedded in phrases like:

• "read FRONT-108"
• "read ticket FEX-23"
• "implement FRONT-108"
• "what is FRONT-108"

Prerequisites

acli must be installed. If a fetch fails because acli is not found, show the user:

acli is not installed. Install it with:

brew install atlassian/tap/atlassian-cli

Then authenticate:

acli jira auth login

Re-run the command once setup is complete.

Do not run which acli before every fetch — only surface this if a command fails.

Steps

1. Fetch ticket with all navigable fields:

   acli jira workitem view <TICKET-KEY> --fields '*all'

2. Extract and summarize the following from the output:

   • Summary — one-line title
   • Type — Bug / Story / Task / Sub-task
   • Status — current workflow state
   • Assignee
   • Description — full acceptance criteria and context
   • Sub-tasks — if any (key + summary)
   • Linked issues — blocks / is blocked by

3. Present a concise brief to the user:

   Ticket: FRONT-108 [Story] · Status: In Progress · Assignee: Tri Tran
   
   Summary: <one-liner>
   
   Description:
   <cleaned-up description>
   
   Sub-tasks / Links: (if any)
   

4. Ask one clarifying question only if critical context is missing after reading the ticket. Otherwise proceed directly to implementation or analysis.

Commands Reference

# Default fields (summary, status, assignee, description)
acli jira workitem view FRONT-108

# All fields
acli jira workitem view FRONT-108 --fields '*all'

# Specific fields
acli jira workitem view FRONT-108 --fields 'summary,description,status,assignee,subtasks,issuelinks'

# JSON output for programmatic use
acli jira workitem view FRONT-108 --json

Common Mistakes

Mistake	Fix
Asking for requirements before reading the ticket	Always fetch first, ask after
Only reading summary line	Fetch --fields '*all' to get acceptance criteria
Ignoring sub-tasks	Check subtasks field — they scope the work
Skipping linked issues	Blockers and related tickets add critical context