CtrlK
BlogDocsLog inGet started
Tessl Logo

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 fetch issue descriptions and comments for analysis. Uses an interactive install gate - if `jira` is missing, ask whether to show installation guidance before any issue commands. Part of the skills-for-java project

77

Quality

71%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/044-planning-jira/SKILL.md
SKILL.md
Quality
Evals
Security

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: For analysis, include description and all comments (or explicitly summarize with omissions noted)

When to use this skill

  • jira issue list
  • List Jira issues
  • Jira JQL issue query
  • jira issue view comments
  • Jira CLI issue workflow

Reference

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

Repository
jabrena/cursor-rules-java
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.