# 044 Planning Jira

> Use when you need the Jira CLI (`jira`) to verify installation, configure Jira Cloud access, list issues (all or by JQL) as markdown tables, and analyze user-provided sanitized Jira summaries. Uses an interactive install gate - if `jira` is missing, ask whether to show installation guidance before any issue commands. This should trigger for requests such as jira issue list; List Jira issues; Jira…

- **Type:** Skill
- **Install:** `agentstack add skill-jabrena-cursor-rules-java-044-planning-jira`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [jabrena](https://agentstack.voostack.com/s/jabrena)
- **Installs:** 0
- **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [jabrena](https://github.com/jabrena)
- **Source:** https://github.com/jabrena/cursor-rules-java/tree/main/skills/044-planning-jira
- **Website:** https://jabrena.github.io/cursor-rules-java/

## Install

```sh
agentstack add skill-jabrena-cursor-rules-java-044-planning-jira
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# 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, and render **markdown tables** from command output. For requirements analysis, use only list metadata plus user-provided 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)
- Issue lists: basic list and 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 `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
- **NO RAW BODY READS**: Do not run Jira commands that retrieve description or comment bodies; use list metadata plus user-provided sanitized summaries for analysis

## When to use this skill

- jira issue list
- List Jira issues
- Jira JQL issue query
- Jira issue summary workflow
- Jira CLI issue workflow

## Workflow

1. **Run interactive install gate**

Check `jira version`; if missing, stop and ask whether the user wants installation guidance before any issue operations.

2. **Verify Jira CLI configuration**

Ensure Jira CLI is configured (site/account/token flow via CLI prompts) before running private workspace commands.

3. **List issues with optional JQL**

Retrieve issues using basic listing or JQL filters and present summaries as markdown pipe tables.

4. **Request sanitized issue context for analysis**

Do not retrieve raw Jira description or comment bodies. If analysis needs detail beyond list metadata, ask the user for a sanitized summary of the relevant Jira issue context and note that raw discussion content was not ingested.

5. **Execute core Jira actions when requested**

Support create, assign, and transition actions using CLI commands while avoiding secret exposure.

## Reference

For detailed guidance, examples, and constraints, see [references/044-planning-jira.md](references/044-planning-jira.md).

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [jabrena](https://github.com/jabrena)
- **Source:** [jabrena/cursor-rules-java](https://github.com/jabrena/cursor-rules-java)
- **License:** Apache-2.0
- **Homepage:** https://jabrena.github.io/cursor-rules-java/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-jabrena-cursor-rules-java-044-planning-jira
- Seller: https://agentstack.voostack.com/s/jabrena
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.