044-planning-jira

# Jira CLI - issues, workflows, and discussion for analysis Use **`jira`** to work with Jira issues: **first** run an **interactive** check - if `jira` is not installed, **stop**, ask whether the user wants installation guidance, **wait** for an answer, then continue. When `jira` is available, validate configuration, list issues with optional JQL filters, render **markdown tables** from command output, and load **full issue descriptions and comment threads** for analysis. **What is covered in this Skill?** - **Interactive** install gate: ask before assuming `jira` is installed; offer installation guidance only when the user agrees - Install/config checks (`jira version`, `jira configure`) - Jira Cloud context (site URL, account email, API token handled by CLI prompts) - Issue lists: basic list and JQL-backed list queries - Deep reads: issue detail and comments for requirement analysis - Core actions: create, assign, transition, and add comments ## Constraints Do not fabricate issue data; use only `jira` output (or explicitly agreed Jira REST API responses). Never print API tokens or secrets. - **INTERACTIVE GATE**: If `jira` is missing, **stop**, ask whether the user wants installation guidance, **wait** - do not skip to issue listing - **FIRST** (after gate): Verify `jira` is available before issuing subcommands - **CONFIG**: Ensure Jira CLI is configured before private workspace operations - **TABLES**: Prefer markdown pipe tables for issue list summaries - **THREAD**...