api
Execute a raw Jira REST API call through the jirac CLI, including GET, POST, PUT, DELETE, and PATCH requests to any Jira REST…
@mulhamnaInstall SkillDevelopment
Skill
/sprint-lifecycle
Manage Jira sprint lifecycle with jirac — list, create, start, complete, update, or delete sprints for a project
Claude Code
$ npx -y skills add mulhamna/jira-commands --skill sprint-lifecycle --agent claude-code
Codex
$ npx skills add mulhamna/jira-commands --skill sprint-lifecycle -a codex -y
Cursor
$ npx skills add mulhamna/jira-commands --skill sprint-lifecycle -a cursor -y
Gemini CLI
$ npx skills add mulhamna/jira-commands --skill sprint-lifecycle -a gemini-cli -y
GitHub Copilot
$ npx skills add mulhamna/jira-commands --skill sprint-lifecycle -a github-copilot -y
OpenCode
$ npx skills add mulhamna/jira-commands --skill sprint-lifecycle -a opencode -y
Windsurf
$ npx skills add mulhamna/jira-commands --skill sprint-lifecycle -a windsurf -y
SKILL.md
sprint-lifecycle.SKILL.mddescription: Manage Jira sprint lifecycle with jirac — list, create, start, complete, update, or delete sprints for a project
Manage the full sprint lifecycle for a Jira scrum board using `jirac`.
Steps: 1. Check that `jirac` is available by running `jirac --version`. If missing, tell the user to install it (`cargo install jira-commands`). 2. Identify the operation:
- **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 <SPRINT_ID> --end-date YYYY-MM-DD`
- **Complete**: `jirac issue sprint-complete -p <PROJECT> --sprint <SPRINT_ID>`
- **Update**: `jirac issue sprint-update -p <PROJECT> --sprint <SPRINT_ID> [--name '<NAME>'] [--goal '<TEXT>'] [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]`
- **Delete**: `jirac issue sprint-delete -p <PROJECT> --sprint <SPRINT_ID>` (destructive — confirm intent)
3. Run `jirac issue sprints -p <PROJECT>` first when the user does not give a sprint ID — the list shows IDs and current state (future / active / closed). 4. Confirm intent before `sprint-start`, `sprint-complete`, and `sprint-delete` — these change visible board state for the whole team.
Notes:
- `--sprint` accepts a sprint name or numeric ID. Use `-p` to select the project, or rely on the configured default project. Starting a sprint also requires `--end-date`; obtain it from the user if missing.
- A board can only have **one active sprint** at a time. `sprint-start` will fail if another sprint is already active.
- `sprint-complete` closes the sprint; any unfinished issues should be moved to a future sprint **before** completing.
- `sprint-delete` permanently removes a sprint and detaches its issues from the sprint field — irreversible.
- For a snapshot of work in a sprint (without changing state), use `jirac issue sprint-summary -p <PROJECT> --sprint '<NAME>'` instead.
Examples:
- "list sprints in PROJ" → `jirac issue sprints -p PROJ`
- "create Sprint 25 in PROJ" → `jirac issue sprint-create -p PROJ --name 'Sprint 25' --goal 'Ship auth v2'`
- "start sprint 42 in PROJ until 2026-06-03" → `jirac issue sprint-start -p PROJ --sprint 42 --end-date 2026-06-03`
- "complete the current sprint in PROJ" → list sprints to find the active ID, then `jirac issue sprint-complete -p PROJ --sprint <ID>`
- "rename sprint 42 in PROJ to 'Sprint 25 (extended)'" → `jirac issue sprint-update -p PROJ --sprint 42 --name 'Sprint 25 (extended)'`
- "delete sprint 99 in PROJ" → `jirac issue sprint-delete -p PROJ --sprint 99` (after confirming)
Read more
description: Manage Jira sprint lifecycle with jirac — list, create, start, complete, update, or delete sprints for a project
Manage the full sprint lifecycle for a Jira scrum board using `jirac`.
Steps: 1. Check that `jirac` is available by running `jirac --version`. If missing, tell the user to install it (`cargo install jira-commands`). 2. Identify the operation:
- **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 <SPRINT_ID> --end-date YYYY-MM-DD`
- **Complete**: `jirac issue sprint-complete -p <PROJECT> --sprint <SPRINT_ID>`
- **Update**: `jirac issue sprint-update -p <PROJECT> --sprint <SPRINT_ID> [--name '<NAME>'] [--goal '<TEXT>'] [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]`
- **Delete**: `jirac issue sprint-delete -p <PROJECT> --sprint <SPRINT_ID>` (destructive — confirm intent)
3. Run `jirac issue sprints -p <PROJECT>` first when the user does not give a sprint ID — the list shows IDs and current state (future / active / closed). 4. Confirm intent before `sprint-start`, `sprint-complete`, and `sprint-delete` — these change visible board state for the whole team.
Notes:
- `--sprint` accepts a sprint name or numeric ID. Use `-p` to select the project, or rely on the configured default project. Starting a sprint also requires `--end-date`; obtain it from the user if missing.
- A board can only have **one active sprint** at a time. `sprint-start` will fail if another sprint is already active.
- `sprint-complete` closes the sprint; any unfinished issues should be moved to a future sprint **before** completing.
- `sprint-delete` permanently removes a sprint and detaches its issues from the sprint field — irreversible.
- For a snapshot of work in a sprint (without changing state), use `jirac issue sprint-summary -p <PROJECT> --sprint '<NAME>'` instead.
Examples:
- "list sprints in PROJ" → `jirac issue sprints -p PROJ`
- "create Sprint 25 in PROJ" → `jirac issue sprint-create -p PROJ --name 'Sprint 25' --goal 'Ship auth v2'`
- "start sprint 42 in PROJ until 2026-06-03" → `jirac issue sprint-start -p PROJ --sprint 42 --end-date 2026-06-03`
- "complete the current sprint in PROJ" → list sprints to find the active ID, then `jirac issue sprint-complete -p PROJ --sprint <ID>`
- "rename sprint 42 in PROJ to 'Sprint 25 (extended)'" → `jirac issue sprint-update -p PROJ --sprint 42 --name 'Sprint 25 (extended)'`
- "delete sprint 99 in PROJ" → `jirac issue sprint-delete -p PROJ --sprint 99` (after confirming)
Ships withjira-commands
Jira on the command line. jirac is a Jira command-line client written in Rust. It ships as a single binary with no runtime dependencies and runs on macOS, Linux, and Windows.
5429 skills
Stars on GitHub
Momentum
- stars in total
- 54
Other skills on jira-commands.
@mulhamnaInstall Skillbatch
Run mixed Jira operations (create, update, transition, archive) from a single JSON manifest file using jirac batch
@mulhamnaInstall Skillbulk-comment
Add the same Markdown comment to multiple Jira issues with jirac, either by JQL query or explicit issue keys
@mulhamnaInstall Skillbulk-create
Create multiple Jira issues at once from a JSON manifest file using jirac bulk-create
@mulhamnaInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about sprint-lifecycle.
- Which coding agents can use sprint-lifecycle?
- sprint-lifecycle installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.