Skip to content
Back to skills

Jira

ASecurity

Jira issues, epics, sprints, backlog and workflow transitions. Use when creating or updating Jira issues, linking epics, moving work through a sprint, or searching the backlog.

  • 80 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 28, 2026
ai-agentsgogit

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned October 5, 2026

npx -y skills add monkilabs/opencastle --skill jira-management --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jira?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Jira
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/monkilabs-jira/badge)](https://www.skillsdirectory.com/skills/monkilabs-jira)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: jira-management
description: "Jira issues, epics, sprints, backlog and workflow transitions. Use when creating or updating Jira issues, linking epics, moving work through a sprint, or searching the backlog."
---

# Task Management with Jira

Project keys, workflow state IDs, and board config: `.opencastle/project/jira-config.md`. Docs: https://developer.atlassian.com/cloud/jira/platform/

## Gotchas

- Transitions are constrained by the project's workflow — a jump the board does not allow fails even with a valid status name. Read the workflow state IDs from `jira-config.md` before transitioning; retry once, then stop.
- Status names in JQL must be quoted when they contain spaces: `status = "In Progress"`.
- A `create` call is only successful if it returns an issue key. Verify before treating the issue as tracked.
- PR-driven status updates only happen when the GitHub/Jira integration is configured; link by putting the key (`PROJ-123`) in the branch or PR title.

## Conventions

Summary format `[Area] Short description` — e.g. `[Schema] Add priceRange field`, `[DB] Add price_range column`, `[UI] Build PriceRangeFilter`, `[Test] E2E price range filtering`.

Every description must carry: **Objective** (one sentence), **Files (partition)** (paths this agent may modify), **Acceptance Criteria** (verifiable checklist), **Dependencies** (issue keys). Group under an Epic; use components or labels for domain grouping.

Flow `Backlog → To Do → In Progress → In Review → Done`. Agent moves `To Do → In Progress` on start, `In Progress → Done` only after verification.

Untracked bug found mid-task: search Jira first; if absent create a `[Bug]` in Backlog with symptoms, repro steps, and affected files.

## JQL

```jql
project = PROJ AND status = "In Progress" ORDER BY priority DESC
project = PROJ AND type = Bug AND status != Done ORDER BY priority DESC
project = PROJ AND sprint in openSprints() ORDER BY priority DESC
project = PROJ AND priority = Highest AND status != Done
```

Session: query in-progress work first → decompose into issues → link dependencies → transition before/after each → on completion verify all Epic issues Done, run build/lint/test, close the Epic.

Files in this skill

  • REFERENCE.md304 B
  • SKILL.md3 KB
  • config.ts928 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…