Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Sprint?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/mulhamna-sprint)
---
name: sprint
description: "Manage Jira sprints and boards, rank issues, and move issues to or from the backlog."
---
Use `jirac --version` to check availability; if missing, tell the user to install `jira-commands`.
- List: `jirac issue sprints -p <PROJECT>`
- Create: `jirac issue sprint-create -p <PROJECT> --name '<NAME>' [--board-id <ID>] [--goal '<TEXT>'] [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]`
- Start: `jirac issue sprint-start -p <PROJECT> --sprint '<ID|NAME>' --end-date YYYY-MM-DD`
- Complete: `jirac issue sprint-complete -p <PROJECT> --sprint '<ID|NAME>'`
- Update: `jirac issue sprint-update -p <PROJECT> --sprint '<ID|NAME>' [--name '<NAME>'] [--goal '<TEXT>'] [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]`
- Delete: `jirac issue sprint-delete -p <PROJECT> --sprint '<ID|NAME>' [--force]`
List sprints first when the target is unclear; use a configured default project
if appropriate. Creation needs `--board-id` when the project maps to multiple
boards. Confirm before start, complete, or delete: these affect the team, and
deletion is irreversible. Use `--force` only after confirmation when the
delete prompt cannot be answered. A board can have only one active sprint;
move unfinished issues as appropriate before completing. For a read-only
snapshot use `jirac issue sprint-summary`.
## Boards and backlog
- List boards: `jirac board list [--project <PROJECT>] [--board-type <TYPE>]`.
- Inspect a board: `jirac board get <ID>`.
- List board issues or backlog: `jirac board issues <ID> [--jql '<JQL>'] [--max <N>]`
or `jirac board backlog <ID> [--jql '<JQL>'] [--max <N>]`.
- Move an issue back to its board backlog with
`jirac issue sprint-remove-issue <KEY>`.
- Rank an issue immediately before or after another issue on its board with
`jirac issue rank <KEY> --before <KEY>` or `--after <KEY>`.