netresearch/jira-skill / skills/jira-communication
jira-communication
FlaggedUse when handling Jira issues, sprints, boards, links, fields, worklogs, attachments, or users, or on any Jira intent without a key ("create/find a ticket", "pick a project"). Auto-triggers on Jira URLs and issue keys (PROJ-123). Also use when MCP Atlassian tools fail or are unavailable for Jira Server/DC.
references/agile.md
View on GitHub<!-- SPDX-License-Identifier: CC-BY-SA-4.0 -->
<!-- SPDX-FileCopyrightText: Netresearch DTT GmbH -->
# Agile — Sprints and Boards
## When to load
Load this reference whenever the user wants to list sprints, list boards, move issues between sprints, or identify the active sprint for a board.
## Boards
```bash
# All boards visible to the authenticated user
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-board.py list
# Filter by project
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-board.py list --project PROJ
# Show only Scrum or Kanban
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-board.py list --type scrum
```
## Sprints
```bash
# Sprints for a specific board (positional BOARD_ID)
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-sprint.py list 119
# Filter by state
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-sprint.py list 119 --state active
# The single currently-active sprint for a board
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-sprint.py current 119
# Issues in a sprint (positional SPRINT_ID)
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-sprint.py issues 916
```
## Assigning an issue to a sprint
The Sprint custom field takes the sprint's integer ID (not its name). Resolve the field's `id` via `jira-fields.py search "sprint"` on your instance; it's typically `customfield_<N>`.
```bash
# Substitute the real custom-field id from `jira-fields.py search "sprint"`
uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-issue.py update PROJ-123 \
--fields-json '{"customfield_SPRINT": 916}'
```
See `issue-editing.md` for more on `--fields-json`, and `fields-and-users.md` for looking up the sprint custom-field ID on other instances.
## Scrum vs Kanban
- **Scrum boards** own named sprints; issues have a Sprint field with an integer ID.
- **Kanban boards** have no sprints — the Sprint field is always empty; `jira-sprint.py list <KANBAN_BOARD_ID>` returns an empty array, not an error.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |