<< All versions
Skill v1.0.1
currentAutomated scan100/100mulhamna/jira-commands/sprint-lifecycle
+3 new
──Details
PublishedNovember 6, 2026 at 08:16 PM
Content Hashsha256:667327f0150ef134...
Git SHA44f9fe7f0c4a
Bump Typepatch
──Files
Files (1 file, 2.7 KB)
SKILL.md2.7 KBactive
SKILL.md · 35 lines · 2.7 KB
description: Manage Jira sprint lifecycle with jirac — list, create, start, complete, update, or delete sprints for a project metadata: version: "1.0.1"
Manage the full sprint lifecycle for a Jira scrum board using jirac.
Steps:
- Check that
jiracis available by runningjirac --version. If missing, tell the user to install it (cargo install jira-commands). - 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)
- 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). - Confirm intent before
sprint-start,sprint-complete, andsprint-delete— these change visible board state for the whole team.
Notes:
--sprintaccepts a sprint name or numeric ID. Use-pto 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-startwill fail if another sprint is already active. sprint-completecloses the sprint; any unfinished issues should be moved to a future sprint before completing.sprint-deletepermanently 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)