Agent skill
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
Install this agent skill to your Project
npx add-skill https://github.com/jabrena/cursor-rules-java/tree/main/skills/044-planning-jira
Metadata
Additional technical details for this skill
- author
- Juan Antonio Breña Moral
- version
- 0.14.0
SKILL.md
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
jirais 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
jirais missing, stop, ask whether the user wants installation guidance, wait - do not skip to issue listing - FIRST (after gate): Verify
jirais 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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
513-frameworks-micronaut-db-migrations-flyway
Use when you need to add or review Flyway database migrations in a Micronaut application — micronaut-flyway, db/migration scripts, flyway.datasources.* configuration, and alignment with JDBC or Micronaut Data. Part of the skills-for-java project
014-agile-user-story
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. Part of the skills-for-java project
502-frameworks-micronaut-rest
Use when you need to design, review, or improve REST APIs with Micronaut — including @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI (OpenAPI Generator), optional runtime OpenAPI via micronaut-openapi, and security annotations. Part of the skills-for-java project
114-java-maven-search
Covers Maven Central search (Search API, maven-metadata.xml, artifact URLs) and project-local update reports via versions-maven-plugin (display-property-updates, display-dependency-updates, display-plugin-updates). Use when finding or verifying coordinates, browsing Central, or checking what newer versions apply to the user’s pom.xml. Part of the skills-for-java project
323-frameworks-spring-boot-testing-acceptance-tests
Use when you need to implement acceptance tests from a Gherkin .feature file for Spring Boot applications — including finding scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for DB/Kafka, and WireMock for external REST stubs. Requires .feature file in context. Part of the skills-for-java project
200-agents-md
Use when you need to generate an AGENTS.md file for a Java repository — covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries — through a modular, step-based interactive process that adapts to your specific project needs. Part of the skills-for-java project
Didn't find tool you were looking for?