Jira Ticket Viewer

jira

Arguments

• $ARGUMENTS[0]

  — Jira issue key (e.g.

  PROJ-123

  )

• $ARGUMENTS[1]

  — (optional) Base directory for all temp assets (raw JSON, attachments, parsed output). Defaults to

  .implement-assets/jira

implement

$ARGUMENTS[1]

.implement-assets/jira

System Requirements

• jira

  CLI installed and configured (https://github.com/ankitpokhrel/jira-cli)

Execution

1. Pre-flight check: Run

   jira me

   to verify the CLI is installed and authenticated — if it fails, follow error handling in references/rules.md. Do NOT continue until

   jira me

   succeeds.
2. Validate

   $ARGUMENTS[0]

   against references/rules.md
3. Fetch raw JSON (single API call): Run

   mkdir -p $ARGUMENTS[1] && jira issue view $ARGUMENTS[0] --raw > $ARGUMENTS[1]/raw.json

   via Bash
4. Parse ticket: Run

   node ./scripts/parse-ticket.js < $ARGUMENTS[1]/raw.json > $ARGUMENTS[1]/output.json

   via Bash to get the parsed JSON output
5. Interpret comments: If the parsed JSON contains a non-empty

   comments

   array, analyze them following references/comment-rules.md. Replace the

   comments

   array in the JSON with a

   commentSummary

   object, then save the updated JSON back to

   $ARGUMENTS[1]/output.json

   using the Write tool.
6. Attachments: If the parsed JSON contains a non-empty

   attachments

   array, download them:
   • Run

     node ./scripts/download-attachment.js --out $ARGUMENTS[1] < $ARGUMENTS[1]/raw.json

     via Bash
   • If

     JIRA_API_TOKEN

     is not set, follow error handling in references/rules.md
   • Include downloaded attachment file paths in the output
7. Return the parsed JSON output (see references/output-format.md for schema reference), including attachment download paths if any