Sprint Lifecycle

Name: Sprint Lifecycle
Author: mulhamna

ASecurity

Manage Jira sprint lifecycle with jirac — list, create, start, complete, update, or delete sprints for a project

50 stars
0 votes
0 copies
4 views
Added May 27, 2026

developmentgo

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add mulhamna/jira-commands --skill sprint-lifecycle --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sprint Lifecycle?

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

Security grade badge for Sprint Lifecycle

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mulhamna-sprint-lifecycle/badge)](https://www.skillsdirectory.com/skills/mulhamna-sprint-lifecycle)

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

---
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 <SPRINT_ID>`
   - **Complete**: `jirac issue sprint-complete <SPRINT_ID>`
   - **Update**: `jirac issue sprint-update <SPRINT_ID> [--name '<NAME>'] [--goal '<TEXT>'] [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]`
   - **Delete**: `jirac issue sprint-delete <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:
- 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" → `jirac issue sprint-start 42`
- "complete the current sprint in PROJ" → list sprints to find the active ID, then `jirac issue sprint-complete <ID>`
- "rename sprint 42 to 'Sprint 25 (extended)'" → `jirac issue sprint-update 42 --name 'Sprint 25 (extended)'`
- "delete sprint 99" → `jirac issue sprint-delete 99` (after confirming)