044-planning-jira

# Jira CLI - issues, workflows, and discussion for analysis Use **`jira`** setup guidance for Jira issue workflows: **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 and ask the Jira project maintainer/operator to provide a sanitized issue inventory. For requirements analysis, use only maintainer-authored sanitized Jira summaries. **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) - Sanitized issue inventories prepared by the Jira project maintainer/operator from basic or JQL-backed list queries - Sanitized Jira summaries supplied by the user for requirement analysis - Core actions: create, assign, and transition ## Constraints Do not fabricate issue data; use only sanitized summaries authored or approved by the Jira project maintainer/operator. 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 ...